Remote MCP Servers

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

Connecting a remote server

In Settings → MCP Servers, scroll to the Add Server form, click the Remote toggle (the alternative is Local), and fill the fields:

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

Then click Connect. The card appears in the list at the top of the page with a status dot.

Preset shortcuts

Above the form, Synapse shows Remote Presets — one-click buttons that pre-fill the form for common services. Click a preset (e.g. Vercel, GitHub Copilot, Slack, Notion, Jira, Zapier, Figma, Fetch) to populate Name/URL and then add your token if the service uses PAT auth, or click Connect straight away for OAuth services.

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. The status pill on the card flips from oauth_pending to connected.

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

Personal Access Token (PAT)

Paste your token into the Token field before clicking Connect. The token is sent as a Bearer header on every request.

Preset remote servers

The presets correspond to the following configurations. You can also recreate them by hand if you need to override anything.

GitHub

• Name: github
• Label: GitHub
• URL: https://api.githubcopilot.com/mcp/
• Token: GitHub PAT with repo scope

Tools include: create/list issues, PRs, comments, branches, file operations.

Advanced: equivalent settings.json entry

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

Jira

• Name: jira
• Label: Jira
• URL: https://mcp.atlassian.com/v1/mcp
• Token: empty (OAuth)

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

Advanced: equivalent settings.json entry

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

Zapier

• Name: zapier
• Label: Zapier
• URL: https://mcp.zapier.com/api/mcp/mcp
• Token: empty (OAuth)

Exposes all your Zapier workflows as tools agents can trigger.

Advanced: equivalent settings.json entry

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

Figma

• Name: figma
• Label: Figma
• URL: https://mcp.figma.com/mcp
• Token: Figma PAT

Tools include: get file, list components, read frames and layers.

Advanced: equivalent settings.json entry

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

Vercel

• Name: vercel
• Label: Vercel
• URL: https://mcp.vercel.com
• Token: empty (OAuth)

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

Advanced: equivalent settings.json entry

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

Fetch

• Name: fetch
• Label: Fetch
• URL: https://remote.mcpservers.org/fetch/mcp
• Token: none required

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

Advanced: equivalent settings.json entry

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

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), click Reconnect on its card. For OAuth servers, this re-opens the browser auth flow; for PAT servers, it retries the existing token. Synapse also shows a Force reconnect option for servers whose session has gone stale.

Connection status

Each MCP server card 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 Settings → Logs