Skip to main content
1

Add the server

The same command is on Workspace settings → MCP endpoint, with a Copy button. Add --scope user to make Citino available in every project on this machine, not only the current one.
2

Sign in

In Claude Code, run /mcp, choose citino and authenticate. Your browser opens Citino’s consent page. It names the app asking, the account you are signed in as and the workspace it will read, and notes that access will be given to an app running on this computer. Choose Allow, and the browser hands you back to Claude Code.
3

Ask

Ask Claude Code about your data in plain language, or have it use Citino’s figures in the work it is doing: “Pull our visibility by engine and draft a summary for the team.”
A signed-in connection reads as you, across the workspace, and Claude Code keeps it alive by itself. To end it, choose Disconnect on Workspace settings → Connected apps.

​
With an API key

For a script, a CI job or a shared machine where nobody signs in, use an API key in a header instead. An owner or admin makes the key on Workspace settings → API keys; it reads what its scopes and projects allow. The MCP tools only read, so the key needs read scopes only.
Run it, paste your key and press Enter. read -rs asks for the key without showing it, so the key stays out of your shell history, and the [ -n … ] check stops the command when nothing was pasted, so it cannot save an empty header.
With a key, Claude Code stores the header in its own configuration. Do not add a key-carrying server with --scope project: that writes the configuration into the project, where it can be committed. Use the default scope or --scope user.

​
Checking it works

claude mcp list shows the server and whether Claude Code can reach it. If it cannot:
  • Signed in: run /mcp again and re-authenticate. A connection unused for 90 days needs signing in again, and one is also ended when its person leaves the workspace or resets their password.
  • With a key: a refused key is answered 401. Check that the key has not been revoked or expired on Workspace settings → API keys, and that the header reached Claude Code’s configuration.

Tools

Every tool and the scope it needs.

Cursor

The same server with a key from Cursor.

Authentication

API keys, scopes and revoking.

How data is handled

What reaches Claude Code, and what never does.