MCP
Model Context Protocol support: serving and optional MCP servers.
v0.20.5source on GitHub
Synapse speaks the Model Context Protocol in two directions: it can serve MCP clients, and it can consume external MCP servers as tools. That makes it both a tool provider for your editor and a tool consumer for your own workflows.
Serving MCP
mcp_serve.py exposes Synapse capabilities to MCP-compatible clients such as editors and other agents.
bash
python3 mcp_serve.pyConsuming MCP servers
- The
optional-mcps/directory bundles optional MCP servers you can enable per profile - MCP is included in the development dependency set (
mcp==2.0.0) - Enable servers through your profile's tool configuration
When to use MCP vs built-in tools
| Situation | Reach for |
|---|---|
| Standard terminal / file / browser work | Built-in tools |
| A service exposes an MCP server already | Consume it via MCP |
| Another agent or editor needs Synapse's abilities | Serve via MCP |
| One-off API integration | Custom skill or script, usually simpler |
See docs/middleware and the feature guides in the repository website docs for advanced MCP routing scenarios.