Use a SyncRange manual MCP token when your client doesn’t support one-click OAuth (Cursor, Claude Desktop config files, Gemini CLI, scripts, and similar). For ChatGPT and Claude’s in-app connectors, prefer the OAuth guides instead.
From your SyncRange dashboard, go to Connections and open AI Assistants (team admins only).
The token is shown once as <prefix>.<secret>. Store it in a password manager. SyncRange only keeps a hash and cannot show it again. If you lose it, revoke and create a new one.
Anyone with the token can read whatever data it’s scoped to until you revoke it. Paste it only into your client’s own configuration — never commit it to git or share it in chat logs.
https://mcp.syncrange.com/mcpBearer <prefix>.<secret>Many editors and desktop apps accept an mcpServers block. Shape:
{
"mcpServers": {
"syncrange": {
"url": "https://mcp.syncrange.com/mcp",
"headers": {
"Authorization": "Bearer <prefix>.<secret>"
}
}
}
}
Exact file location and field names vary (e.g. Cursor MCP settings, Claude Desktop config). If your client asks for “remote MCP” or “HTTP MCP”, point it at the URL above and add the Authorization header.
Gemini CLI uses httpUrl for Streamable HTTP servers:
gemini mcp add --transport http \
--header "Authorization: Bearer <prefix>.<secret>" \
syncrange https://mcp.syncrange.com/mcp
Or in settings.json:
{
"mcpServers": {
"syncrange": {
"httpUrl": "https://mcp.syncrange.com/mcp",
"headers": {
"Authorization": "Bearer <prefix>.<secret>"
}
}
}
}
More Gemini context (including Gemini Enterprise UI): Connect Gemini.
Successful reads show up under SyncRange Connections → AI Assistants (token last used, and active data connections).
<prefix>.<secret>, including the dot.Authorization: Bearer … (with a space after Bearer).Confirm the URL is https://mcp.syncrange.com/mcp and your client is using HTTP/streamable MCP (not a local stdio command pointing at a missing binary).