Connect Claude

Add SyncRange as a custom remote MCP connector in Claude, complete OAuth, then ask about your connected data in chat. SyncRange tools are read-only.

What you'll need

Access to claude.ai (custom connectors are available on Free, Pro, Max, Team, and Enterprise; Free is limited to one custom connector).
A SyncRange team with at least one data source already connected, and team admin access to approve OAuth consent.

Claude’s menu paths may say Customize → Connectors or Settings → Connectors. Team/Enterprise owners add connectors under admin settings first.

MCP server URL

https://mcp.syncrange.com/mcp

Leave advanced OAuth Client ID / Secret blank unless SyncRange has given you dedicated credentials. Claude discovers SyncRange’s OAuth server automatically from the MCP endpoint.

Pro, Max, and Free (individual)

Open Connectors
In Claude, go to Customize → Connectors (or Settings → Connectors).
Add a custom connector
Click + / Add custom connector. If asked for a type, choose the web / remote MCP option.
Enter SyncRange details
- Name — e.g. SyncRange
- Remote MCP server URL — https://mcp.syncrange.com/mcp
You usually do not need to fill Advanced OAuth Client ID / Secret — SyncRange supports dynamic client registration for this flow.
Add, then Connect
Click Add. Find the SyncRange connector in your list and click Connect so Claude can start OAuth.
Sign in and authorize on SyncRange
Your browser opens SyncRange. Log in if needed, choose the team, review scopes (which data sources Claude may read), and click Authorize.
Chat with your data
Return to Claude and ask a normal question, e.g. "Summarize my Meta ads performance this week." Enable the connector for the conversation if Claude shows a per-chat tools toggle.

Team and Enterprise

Owner adds the connector
An Owner (or Primary Owner) opens Admin settings → Connectors (or Organization settings → Connectors), clicks Add custom connector, enters https://mcp.syncrange.com/mcp, and saves.
Each member connects
Members open Settings → Connectors (or Customize → Connectors), find SyncRange under custom connectors, and click Connect to complete their own SyncRange OAuth consent.
Use in chat
Enable the connector when chatting, then ask about your connected sources.

Remote vs local

Custom connectors call SyncRange from Anthropic’s cloud over HTTPS. For a local JSON config with a pasted bearer token (Claude Desktop manual MCP config), use the CLI & local clients guide instead.

After you connect

The connection appears on SyncRange under Connections → AI Assistants. Revoke it there to cut off access immediately.
You can also disconnect the connector in Claude’s Connectors UI.
OAuth tokens refresh automatically.

Troubleshooting

Connect fails or OAuth never opens

Confirm the URL is exactly https://mcp.syncrange.com/mcp (HTTPS, ends with /mcp).
On Team/Enterprise, confirm an Owner has added the custom connector before members try to Connect.

Claude connects but can't read a source

Re-check the scopes you approved on SyncRange’s consent screen.
Confirm the underlying account is still active under SyncRange Connections.

I need a static bearer token instead

Some Claude Desktop / local setups use a manual token. See CLI & local clients. Request-header auth for remote Claude connectors may also be available depending on Anthropic’s rollout — OAuth remains the recommended path for SyncRange.