Add SyncRange as a custom MCP connector in ChatGPT, sign in with OAuth, then ask about your connected data in a normal chat. SyncRange tools are read-only.
OpenAI’s UI labels move occasionally — you may see Connectors, Apps, or Apps & Connectors. The steps below use the common current paths.
https://mcp.syncrange.com/mcp
Choose OAuth if ChatGPT asks for an authentication method. You do not need a manual SyncRange token for this flow.
In ChatGPT, open Settings → Apps & Connectors → Advanced settings (wording may vary) and turn on Developer Mode. Without this, the option to add a custom MCP connector is usually hidden.
Go back to Settings → Apps & Connectors and choose Create / Add custom connector.
SyncRangehttps://mcp.syncrange.com/mcpChatGPT will warn that custom MCP servers are not verified by OpenAI. Confirm only if you trust SyncRange as the operator of this endpoint.
Your browser opens SyncRange. Log in if needed, choose which team to connect, review the data sources (scopes), and click Authorize. ChatGPT receives an access token automatically — you never copy a secret.
Start a new conversation. Open the tools / apps control for that chat and enable the SyncRange connector. Then ask something like: "What were my Shopify sales last month?"
Plus and Pro users may be limited to read/fetch-style custom connectors. SyncRange only exposes read tools, so this matches how our MCP server works.
A workspace admin may need to allow Developer Mode / custom MCP connectors under workspace permissions (labels vary by plan).
In workspace connector settings, create a connector named SyncRange with URL https://mcp.syncrange.com/mcp, then publish or share it with members as your org policy requires.
Members open Settings → Apps & Connectors, find SyncRange, click Connect, and complete the SyncRange OAuth consent for their team.
In each chat, turn the SyncRange app/connector on before asking data questions.
Confirm Developer Mode is on (Plus/Pro), or that a workspace admin has enabled custom MCP connectors for your plan.
ChatGPT’s custom connector flow is built around OAuth. For clients that take a bearer token in JSON config, see CLI & local clients.