Two ways to connect
Connect Claude
claude.ai and Claude Desktop, by signing in.
Connect ChatGPT
ChatGPT, by signing in.
Claude Code
Sign in from the terminal, or use a key for a machine nobody signs in on.
Cursor
With an API key.
What it can do, and what it cannot
- It reads, and only reads. There are no write tools. To add prompts or change competitors from code, use the REST API’s writes with a key.
- It returns numbers, names and dates, never an engine’s answer text. Every figure comes with its ± band, its sample size and whether a change is within noise, exactly as the dashboard shows it. See How data is handled.
- Each tool is the twin of one REST route, reading the same data with the same scope. See Tools.
- It counts against your API budgets. A sign-in connection has its own budget a minute, the same size as a new key’s, and shares the workspace’s budget with every key. Report tools count as several requests, as their REST routes do. See Rate limits.
Who can connect
Any team member can connect by signing in. A client portal login cannot: it reads its agency’s reports and nothing else. If you belong to more than one workspace, the sign-in page lets you choose which one the app reads.Managing connections
Workspace settings → Connected apps lists the apps connected by signing in: your own, or everyone’s if you are an owner or admin. Disconnect ends a connection at once; the app’s next call fails. A connection also ends when its person leaves the workspace or resets their password. While it is in use, the app keeps it alive by itself; one left unused for 90 days needs signing in again. A key connection ends when the key is revoked on Workspace settings → API keys.Related
Tools
Every tool, its scope and its REST twin.
How data is handled
What crosses into your assistant, and what never does.
Authentication
API keys and their scopes.
Workspace settings
The MCP endpoint, API keys and Connected apps.