-
-
Notifications
You must be signed in to change notification settings - Fork 52
MCP Servers
Synapse supports connecting to any MCP (Model Context Protocol) server. Any MCP-compatible API or tool becomes an agent tool instantly.
Connect to MCP servers over the network — no code needed.
To add a remote server:
- Open Settings → MCP Servers
- Click the Remote (URL) tab at the top of the form
- Optionally select a preset to auto-fill the URL and token fields
Available presets: Vercel, GitHub Copilot, Jira, Zapier, Figma, Fetch
- Enter a Server Name and the Server URL
-
Authentication:
- Leave Bearer Token empty to use OAuth (a browser window opens for authorization)
- Paste a Personal Access Token (PAT) for PAT-based servers (GitHub, Figma)
- Click Connect Server
Synapse prefixes external tools with <server-name>__<tool-name> to prevent naming collisions.
| Field | Value |
|---|---|
| Server Name | github |
| Server URL | https://api.githubcopilot.com/mcp/ |
| Bearer Token | Your GitHub PAT |
After connecting, agents can use github__create_issue, github__list_repos, etc.
For servers that run as local processes, use the Local (stdio) tab:
| Field | Example |
|---|---|
| Server Name | git |
| Command | uvx |
| Arguments | mcp-server-git |
| Environment Variables | GIT_AUTHOR_NAME=My Agent |
Add environment variables (API keys, secrets) directly in the form — no config file editing required.
Built-in presets for local servers: Git, filesystem, and others.
Command: python
Arguments: /path/to/my_mcp_server.py
Env Vars: MY_API_KEY=secret
Browse the MCP servers registry for community-built servers covering:
- GitHub, GitLab, Jira
- Slack, Linear, Notion
- Databases (Postgres, SQLite)
- Web search, fetch
- File systems, cloud storage
- And hundreds more
When a remote MCP server named jira exposes a tool called create_ticket, it becomes:
jira__create_ticket
This prefix prevents conflicts when multiple servers expose similarly-named tools.
For servers that use OAuth (e.g., GitHub Copilot, Zapier):
- Leave the Bearer Token field empty
- Click Connect Server
- A browser window opens for authorization
- After approval, Synapse stores the token and handles refresh automatically
- Local (stdio): Synapse spawns the process and communicates over stdin/stdout
- Remote (HTTP): Uses Streamable HTTP (SSE) transport with OAuth 2.0 PKCE or Bearer token auth
- Token refresh and session lifecycle are managed automatically
- Built-in Tools — tools that ship with Synapse
- Custom Tools — build tools from webhooks or Python scripts