Project Synapse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the application | INFO |
| NEO4J_URI | Yes | URI for connecting to the Neo4j database | bolt://localhost:7687 |
| NEO4J_USER | Yes | Username for the Neo4j database | neo4j |
| NEO4J_DATABASE | No | Name of the Neo4j database to use | neo4j |
| NEO4J_PASSWORD | Yes | Password for the Neo4j database |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debug_testB | Simple test tool to check if MCP server is working. |
| ingest_textB | Ingest and process text into the knowledge graph using semantic analysis. This tool performs the core knowledge synthesis pipeline:
Args: text: Raw text to process and analyze source: Source identifier for provenance tracking metadata: Additional metadata about the text Returns: Processing summary with entities and relationships extracted |
| generate_insightsC | Trigger autonomous insight generation using the Zettelkasten engine. This tool activates the autonomous synthesis engine to identify patterns and generate novel insights from the existing knowledge graph. Args: topic: Optional topic to focus insight generation on confidence_threshold: Minimum confidence level for insights (0.0-1.0) Returns: Generated insights with confidence scores and evidence trails |
| query_knowledgeA | Query the knowledge graph for facts and insights using natural language. This tool provides the conversational interface to the knowledge base, prioritizing synthesized insights over raw facts. Args: query: Natural language query include_insights: Whether to include AI-generated insights max_results: Maximum number of results to return Returns: Query results with facts, insights, and reasoning trails |
| explore_connectionsB | Explore connections and relationships around a specific entity in the knowledge graph. This tool implements the graph traversal capabilities for discovering non-obvious connections and patterns. Args: entity: Entity name to explore from depth: How many relationship hops to explore (1-5) connection_types: Specific relationship types to follow Returns: Visual representation of connections and discovered patterns |
| analyze_semantic_structureB | Analyze the semantic structure of text using Montague Grammar parsing. This tool provides insight into the formal semantic analysis capabilities and shows the logical form translations. Args: text: Text to analyze semantically include_logical_form: Whether to include the formal logical representation Returns: Semantic analysis with entities, relations, and optional logical forms |
| wiki_list_pagesB | List all markdown pages in the wiki vault with pagination. Args: subdir: Subdirectory to list ('wiki' or 'raw'). limit: Maximum pages to return (default 50, max 200). offset: Offset for pagination. tag: Filter by tag. |
| wiki_read_pageB | Read a wiki page. Args: path: Relative path from vault root (e.g. 'wiki/concepts/rag.md'). mode: What to return: - "meta": metadata/frontmatter only (from index, 0 file reads) - "excerpt": metadata + first 500 characters of page body (from index) - "full": complete page content (reads file from disk) |
| wiki_write_pageB | Write or update a wiki page with frontmatter. Args: path: Relative path (e.g. 'wiki/entities/neo4j.md'). body: Markdown body content. summary: One-line summary for the index. tags: Comma-separated tags. |
| wiki_searchA | Search wiki pages by keyword. Args: query: Space-separated search terms. limit: Maximum results to return (default 10). subdir: Scope to subdirectory. |
| wiki_sync_indexA | Refresh the wiki index database from disk. Runs automatically on server start and after write operations. Call manually if files were changed outside Synapse (e.g., Obsidian edits, git pull). |
| wiki_lintA | Run a health check on the wiki vault. Detects orphan pages, broken wikilinks, and missing frontmatter. |
| wiki_hits_analysisA | Compute HITS hub and authority scores on the wiki wikilink graph. Authorities = pages cited by many others — load-bearing knowledge nodes. Hubs = pages that link to many good authorities — navigation layers. Use to identify which pages need deepening (high authority) and which need comprehensive link coverage (high hub). |
| wiki_cluster_pagesA | Cluster wiki pages by semantic similarity using GAAC (TF-IDF). Identifies:
Args: n_clusters: Number of clusters (auto = sqrt of page count if omitted). |
| wiki_update_indexB | Rebuild the wiki index from all wiki pages. Args: deep: If True, performs a disk-level verification of all indexed files. |
| wiki_ingest_rawA | Read a raw source file and ingest it into both the knowledge graph and wiki. Reads from raw/, runs it through the Synapse semantic pipeline, stores in Neo4j, and creates a summary page in wiki/sources/. Args: filename: Filename inside the raw/ directory. |
| wiki_fetch_urlA | Fetch a URL with defuddle (clean markdown extraction), save to raw/, ingest into the knowledge graph, and archive to Clippings/. Use this when researching the web — it strips navigation and clutter, leaving only the article content. Much cleaner than raw web_fetch. Args: url: The URL to fetch and process. ingest: If True (default), immediately ingest into Neo4j after saving. Set False to save to raw/ only for manual review first. |
| synapse_rememberA | Record a time-stamped fact in Synapse's episodic memory. Use this whenever something is worth remembering across sessions: decisions, observations, "Ty said X on date Y", health/diet/symptom log entries, project milestones. Args: subject: Who or what the fact is about. Free-form name. predicate: The relationship verb. snake_case preferred (e.g. "started_taking", "moved_to", "decided_to_use"). object: The other side of the relation. valid_from: ISO date or datetime when the fact became true. If omitted, "now" is used. Bare dates → midnight UTC. valid_to: ISO date or datetime when the fact stopped being true. Omit for still-current facts. confidence: 0–1. Default 1.0 for explicit user statements; lower when the agent is inferring. source: Where this fact came from. Defaults to "agent:claude" for things Claude is recording. Use "user" or a filename for facts from explicit user statements or document ingestion. note: Free-form context. Stored in metadata for later recall. Returns: The fact id (stable content hash — safe to call twice). |
| synapse_recallA | Look up time-stamped facts about an entity. Args:
entity: Name to look up. Matches subject, object, or both depending
on Returns: Newline-separated list of facts with timestamps. Empty if none found. |
| synapse_timelineA | Chronological view of remembered facts. Args: entity: Scope to one entity, or None for the global timeline. limit: Max number of rows. Default 50. Returns: Time-ordered fact list, oldest first. |
| synapse_invalidateA | Mark a previously-recorded fact as no longer true. Sets Args: subject/predicate/object: The triple to invalidate. ended: ISO date/datetime when the fact stopped being true. Defaults to now if omitted. Returns: Number of facts affected. |
| synapse_causal_windowA | Find candidate causes by temporal correlation. Surfaces facts whose This is exactly the "track everything you ate to find what caused the headaches" pattern — you record symptom onset, you record meals and medications, then this tool surfaces co-occurring events as candidates. The tool returns correlation; the human (or a downstream reasoning step) decides what caused what. Args: effect_entity: The thing whose causes you're hunting (e.g. "headache", "rash", "build failure"). before: ISO date/datetime — when the effect was observed. within_days: How far back to search. Default 30. Returns: Ranked list of candidate cause-effect pairings with day deltas. |
| synapse_memory_statsA | Quick stats: how many temporal facts are stored, time span covered. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| knowledge_synthesis_prompt | Generate a prompt for synthesizing knowledge about a specific topic. Args: topic: The topic to synthesize knowledge about context: Additional context or constraints Returns: Structured prompt for knowledge synthesis |
| semantic_analysis_prompt | Generate a structured prompt for deep semantic analysis using Montague Grammar principles. Args: text: Text to analyze Returns: Multi-turn conversation for comprehensive semantic analysis |
| insight_validation_prompt | Generate a prompt for validating AI-generated insights against evidence. Args: insight: The insight to validate evidence: Supporting evidence Returns: Validation prompt for insight assessment |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| knowledge_statistics | Provides current statistics about the knowledge graph and synthesis engine. Returns real-time metrics about: - Total entities and relationships - Generated insights count - Processing statistics - System health metrics |
TDQS
Scored across 23 tools
The tools are grouped into wiki, knowledge graph, and memory domains, but several have blurry boundaries: wiki_sync_index vs wiki_update_index, synapse_recall vs synapse_timeline, and ingest_text vs wiki_ingest_raw could cause misselection. Descriptions help clarify most overlaps, but not all.
Most tools follow verb_noun snake_case with clear wiki_ and synapse_ prefixes, but the core knowledge graph tools (ingest_text, query_knowledge, explore_connections) lack a shared prefix and debug_test breaks the pattern. The naming is mostly consistent but not fully systematic.
23 tools is in the heavy range and requires a lot of surface area to navigate, though each tool has a plausible role in the wiki/knowledge-graph/memory system. It is borderline: not overwhelming, but more than is clearly necessary.
The set covers wiki read/write/indexing, knowledge graph ingestion and querying, and episodic memory lifecycle management including invalidation and causal analysis. Minor gaps exist (no wiki page deletion, no explicit knowledge graph entity update/delete), but core workflows are well covered.