Scorra

Connecting Scorra to Claude, Cursor or n8n

The MCP server: what it is, how to connect it, and what to ask once you have

What MCP gives you

Model Context Protocol lets an AI client — Claude, Cursor, n8n, or anything else that speaks it — read your Scorra data directly. Instead of exporting a CSV and pasting it into a chat, you ask the question where you already work:

> Which questions did we lose visibility on this month, and which sources are behind that?

The client calls Scorra, gets the real numbers, and answers from them.

Availability

Machine access — MCP, the API and API keys — is included from Growth upwards. It is also on during the trial, so you can test it before committing.

If your plan does not include it, the server answers with a 403 and a sentence saying so, rather than failing silently. A connection made on a higher plan stops working after a downgrade.

Connect in three steps

1. Add the server

https://app.getscorra.com/api/mcp

In Claude, that is Settings → Connectors → Add custom connector. In other clients, look for "MCP servers" or "custom tools".

2. Sign in

Clients that support OAuth will open a Scorra sign-in page and ask you to authorise the connection. Nothing is pasted anywhere — approve it and the client stores the token.

For clients without OAuth, create an API key in Settings → API keys and send it as Authorization: Bearer <key>.

3. Ask something

> What is our visibility on ChatGPT over the last 30 days, and which competitors are ahead > of us?

If the client lists Scorra's tools, the connection works.

Changes need a second call

Read tools answer immediately. Tools that change something — adding a tracked question, posting to Slack — never act on the first call. They return a plan of what they would do plus a confirmation token, and only a second call carrying that token performs the change.

The token is signed over the exact input, so a confirmation for remove question A cannot execute remove question B, and it expires after 15 minutes. Your AI client shows you the plan and asks before sending the second call.

If it does not connect

  • 403 with a message about your plan — machine access starts at Growth.
  • 401 — the key is wrong, revoked, or sent in the wrong header.
  • The client sees no tools — a read-only key hides the write tools by design. Check the key's scopes in Settings → API keys.
  • Changing `AUTH_URL` invalidates existing OAuth connections; clients must reconnect.

All help articles