Remote MCP Servers

Remote MCP servers are accessed via HTTP and are typically hosted by third-party services. Authentication is via OAuth 2.0 or a Personal Access Token (PAT).

Connecting a remote server

Go to Settings → MCP Servers → Add Server and choose Remote (URL).

Fields

Field	Description
Name	Unique identifier (used as tool prefix)
Label	Human-friendly display name
URL	The MCP server endpoint URL
Token	PAT (if the server supports token auth). Leave blank to trigger OAuth.

Authentication modes

OAuth 2.0

Leave the Token field empty. When you click Connect, Synapse opens a browser window for the OAuth flow. After you authorise, the browser closes automatically and the server connects.

OAuth tokens are cached in DATA_DIR/google-credentials/ and refreshed automatically.

Personal Access Token (PAT)

Enter your PAT in the Token field. The token is sent as a Bearer token in API requests.

Preset remote servers

Synapse ships with preset configurations for popular services — click Add Preset to see them:

GitHub

{
  "name": "github",
  "label": "GitHub",
  "server_type": "remote",
  "url": "https://api.githubcopilot.com/mcp/",
  "token": ""
}

Requires a GitHub PAT with repo scope. Tools include: create/list issues, PRs, comments, branches, file operations.

Jira

{
  "name": "jira",
  "label": "Jira",
  "server_type": "remote",
  "url": "https://mcp.atlassian.com/v1/mcp",
  "token": ""
}

OAuth-based. Tools include: create/update issues, search JQL, manage sprints, add comments.

Zapier

{
  "name": "zapier",
  "label": "Zapier",
  "server_type": "remote",
  "url": "https://mcp.zapier.com/api/mcp/v1",
  "token": ""
}

OAuth-based. Exposes all your Zapier workflows as tools agents can trigger.

Figma

{
  "name": "figma",
  "label": "Figma",
  "server_type": "remote",
  "url": "https://www.figma.com/api/mcp",
  "token": "YOUR_FIGMA_PAT"
}

Requires a Figma PAT. Tools include: get file, list components, read frames and layers.

Vercel

{
  "name": "vercel",
  "label": "Vercel",
  "server_type": "remote",
  "url": "https://vercel.com/mcp",
  "token": ""
}

OAuth-based. Tools include: list deployments, promote environments, manage environment variables.

Fetch

{
  "name": "fetch",
  "label": "Fetch",
  "server_type": "remote",
  "url": "https://fetch.mcp.cloudflare.com",
  "token": ""
}

No auth required. A simple HTTP fetch tool — agents can make GET/POST requests to any URL. Useful for agents that need to call arbitrary APIs.

OAuth callback

Synapse hosts an OAuth callback at http://localhost:8000/api/mcp/oauth/callback. When setting up OAuth apps (e.g. GitHub OAuth App, Google Cloud OAuth), add this as an allowed redirect URI.

Reconnecting

If a remote server disconnects (e.g. token expired), use the Reconnect button in Settings → MCP Servers. For OAuth servers, this re-triggers the browser auth flow.

Connection status

Each MCP server shows one of these statuses:

Status	Meaning
connected	Active and tools are available
disconnected	Not connected — use Reconnect
oauth_pending	OAuth flow in progress
error	Connection failed — check logs