Synapse MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | Project root directory (default: current working directory) | |
| logLevel | No | debug | info | warn | error (default: info) | info |
| maxFileSize | No | Skip files larger than this (default: 524288 = 512 KB) | 524288 |
| maxTreeDepth | No | Maximum directory depth for tree view (default: 5) | 5 |
| maxSearchResults | No | Cap on search results returned (default: 50) | 50 |
| maxDependencyDepth | No | Import hops for semantic context (default: 2) | 2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_treeA | Returns a structured tree view of the project repository, respecting .gitignore rules. |
| get_semantic_contextB | Returns the content of a file along with its local dependency tree, providing rich context for understanding the code. |
| search_codebaseA | Searches the codebase for text or regex patterns, returning matches with file paths and line numbers. |
| get_changed_filesA | Returns a list of files changed since a git ref (default: HEAD~1), grouped by status (added/modified/deleted). Optionally includes the full unified diff. Use this to understand what changed in a branch or commit. |
| get_project_indexA | Returns a compressed semantic map of the entire project: all exported functions, classes, interfaces, and types with their signatures — no implementation bodies. Ideal for getting an overview of a large codebase in a single call (~500 tokens). Call this first when exploring an unfamiliar project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: changes, semantic index, tree structure, file context with dependencies, and text search. No overlap.
Most tools follow 'get_<noun>' pattern, but 'search_codebase' uses a different verb. However, all names are snake_case and descriptive, with minor inconsistency.
Five tools is ideal for a code exploration server, covering the key tasks without bloat.
Core exploration needs are met (changes, overview, structure, context, search). Minor gaps like call hierarchy or references exist but are beyond basic requirements.