
angrysky56/project-synapse-mcp
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Transforms raw text into interconnected knowledge graphs and autonomously generates insights through advanced pattern detection.
Обзор
Project Synapse is an MCP (Model Context Protocol) server that combines a Neo4j 2026.x graph database with an Obsidian Markdown wiki to create a persistent, compounding knowledge base. Raw text is processed through a semantic pipeline into interconnected graph nodes with vector embeddings, while a human-readable wiki layer provides browsable, interlinked Markdown pages. For detailed information on setting up and using Project Synapse, please refer to the following guides: - : Installation and first run. - : How the semantic pipeline and graph work. - : Full list of environment variables. - : Guide for adding tools and contributing. - : Running the test suite. - : Project contribution guidelines. It's for the thinking, research, and writing that surrounds projects — architecture decisions, domain research, design rationale, reference material, meeting notes. Code lives in its repo. Knowledge about the code lives here.
README
Показан фрагмент оригинального README. Открыть оригинал.
🧠 Project Synapse MCP Server
Autonomous Knowledge Synthesis Engine with LLM-WIKI Integration
Project Synapse is an MCP (Model Context Protocol) server that combines a Neo4j 2026.x graph database with an Obsidian Markdown wiki to create a persistent, compounding knowledge base. Raw text is processed through a semantic pipeline into interconnected graph nodes with vector embeddings, while a human-readable wiki layer provides browsable, interlinked Markdown pages.
📚 Documentation
For detailed information on setting up and using Project Synapse, please refer to the following guides:
- Getting Started: Installation and first run.
- Architecture: How the semantic pipeline and graph work.
- Configuration: Full list of environment variables.
- Development: Guide for adding tools and contributing.
- Testing: Running the test suite.
- Contributing: Project contribution guidelines.
What This Is (and Isn’t)
This is a knowledge system, not a code editor. It’s for the thinking, research, and writing that surrounds projects — architecture decisions, domain research, design rationale, reference material, meeting notes.
Code lives in its repo. Knowledge about the code lives here.
Use cases:
- Research deep-dives that accumulate over weeks/months
- Project knowledge bases (why decisions were made, not just what)
- Personal knowledge management (articles, books, podcast notes)
- Collaborative brainstorming with AI as the wiki maintainer
Per-project setup: Create a separate Obsidian vault + GitHub repo for each project. Point the WIKI_VAULT_PATH env var at it. One Neo4j instance can serve multiple projects (graphs coexist).
Architecture
Web / Raw Sources
│
[defuddle] ← cleans web content before ingestion
│
▼
┌──────────────────────┐ ┌─────────────────────┐
│ Semantic Pipeline │────▶│ Neo4j Knowledge │
│ (Montague Grammar, │ │ Graph (entities, │
│ NLP, embeddings) │ │ facts, vectors) │
└──────────────────────┘ └────────┬────────────┘
│
┌───────┴───────┐
│ Wiki Adapter │
└───────┬───────┘
│
┌───────▼───────┐
│ Obsidian Vault│
│ (Markdown, │
│ Git-synced) │
└───────────────┘
Key Features
Knowledge Graph (Neo4j 2026.x)
- Native VECTOR type with ANN semantic search
- Fulltext BM25 indexes for keyword search
Установка
This server does not publish a one-line install command.
Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →Конфигурация
{
"mcpServers": {
"project-synapse": {
"command": "uv",
"args": [
"--directory",
"/path/to/project-synapse-mcp",
"run",
"python",
"-m",
"synapse_mcp.server"
]
}
}
}