Connect Revolutio to Claude

How it works

Claude talks to Revolutio over the Model Context Protocol using a secure OAuth 2.1 connection. You authorise Claude once through a sign-in flow, and Claude receives a token to call Revolutio on your behalf.

Each search consumes Revolutio credits the same way an API call does.
Every tool call is recorded in your account audit log.
You can revoke access at any time from your Revolutio settings or from Claude's connector list.

Connect Revolutio to Claude

Open Claude → Settings → Connectors → Add custom connector.
Fill in:
- Name: Revolutio
- Remote MCP server URL: https://mcp.revolutio.systems/mcp
- Advanced settings: leave OAuth Client ID and OAuth Client Secret blank — the connector self-registers.
Click Add. A new browser tab opens for sign-in.
Sign in to Revolutio with your account email and password. (If you're already signed in elsewhere, this step is skipped.)
On the consent screen, click Allow. The tab closes automatically.
Back in Claude, Revolutio now appears in the connector list with 2 tools available.

Connection takes about thirty seconds end-to-end. If a step doesn't progress, see Troubleshooting below.

Use it

Open a new chat and ask:

"What are my most recent Revolutio cases?"

"How many cases have I created in the last 30 days?"

"Look up KIRKBI A/S in Denmark."

"Find the company with registration number 12345678 in the UK."

Claude will call the Revolutio tools, show what it's doing, and summarise the results in natural language.

Available tools

Tool	Purpose	Consumes credits?
`list_cases`	List your most recent KYC/KYB cases (target name, jurisdiction, search counts, officer/shareholder counts, timestamps).	No
`search_company`	Look up a company in its national registry — same as a `/search` API call. Returns the official record (legal name, addresses, officers, shareholders, etc.).	Yes — same per-jurisdiction cost as the API

Disconnect

You can revoke Claude's access from either side:

From Claude: Settings → Connectors → Revolutio → Remove.
From Revolutio: client.revolutio.systems → Settings → Connected Apps → Revoke next to "Claude".

The connector stops working within seconds. Reconnecting is a repeat of the connect flow above.

Troubleshooting

Connector shows "0 tools available" after adding

Sign-in or consent didn't complete cleanly. Remove the connector from Claude's settings and add it again.

Tool calls hang for several minutes

Some national registries are slow — Hong Kong, Netherlands (with credentials), Japan can take 3–5 minutes. The search may still complete server-side; check Revolutio's webapp folio after a few minutes, or retry the same prompt.

"Insufficient Revolutio credits"

You're out of credits. Top up by signing in to client.revolutio.systems and going to Settings → Subscription Details. list_cases does not consume credits, so this only applies to search-style tools.

Sign-in tab opens but shows "Authorization error"

The OAuth setup likely got stale. Remove the Revolutio connector from Claude and add it again — a fresh client will be issued.

Programmatic / API access

If you want to use Revolutio from Cursor, your own scripts, CI, or any other context where the OAuth-browser flow doesn't apply, generate a personal API key in Settings → API Keys → Manage API keys. The API key is a long-lived bearer token you can paste into any MCP-compatible client. See your client's documentation for the configuration shape — typically:

{
  "type": "streamable-http",
  "url": "https://mcp.revolutio.systems/mcp",
  "headers": {
    "Authorization": "Bearer rev_xxxxxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  }
}

API keys and OAuth grants coexist: revoking one doesn't affect the other.

Connect Revolutio to Claude

How it works

Prerequisites