Connect via CLI & local clients

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.

When to use this guide

  • ChatGPT and Claude web UIs → use OAuth custom connectors.
  • Cursor, VS Code-style MCP config, Claude Desktop JSON, Gemini CLI, curl → use this page.

Create a manual token

  1. Open AI Assistants

    From your SyncRange dashboard, go to Connections and open AI Assistants (team admins only).

  2. Fill in the New Token form
    • Name — a label you’ll recognize later (e.g. "Cursor on laptop").
    • Client — Cursor, Claude, Gemini, ChatGPT, or Other (informational only; it doesn’t restrict which client can use the token).
    • Scopes — tick each data source this token may read. See the data reference for available tools.
  3. Copy your token

    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.

Treat your token like a password

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.

Server URL and auth header

  • Server URLhttps://mcp.syncrange.com/mcp
  • Authorization headerBearer <prefix>.<secret>

Generic MCP JSON (Cursor, Claude Desktop, and similar)

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

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.

Verify the connection

  1. Restart or reload MCP servers in your client if required.
  2. Confirm SyncRange tools appear (names typically include sources like Shopify, Meta, Google Analytics).
  3. Ask a simple question, e.g. "List my connected SyncRange accounts" or "What were my Shopify sales last week?"

Successful reads show up under SyncRange Connections → AI Assistants (token last used, and active data connections).

Revoking and rotating

  • On Connections → AI Assistants, click Revoke on a token to disable it immediately.
  • Revoking cannot be undone — create a new token and update every client config that used the old value.

Troubleshooting

Client says unauthorized / no access

  • Confirm you pasted the full <prefix>.<secret>, including the dot.
  • Confirm the header is Authorization: Bearer … (with a space after Bearer).
  • Confirm the token wasn’t revoked and scopes include the source you’re asking about.

Tools never appear

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).

Related Documentation

Stop Juggling Dashboards. Start Growing Get your data flowing today, free plan available.