Skip to main content

Before You Start

You need an active Clara account with the Admin or Bookkeeper role. No token or API key required — you’ll authenticate directly with your Clara account (the same login you use on the platform) during setup.

Server URLs by Country

Each Clara market has its own MCP server URL. Use the one that matches your Clara account: All servers use the same OAuth login flow — no custom headers or static tokens required.
The setup process is identical for Claude Web and Claude Desktop.

New Users

On Team/Enterprise Claude accounts, your organization may restrict custom connector setup to Administrators only.
  1. Go to Settings → Connectors.
  2. In the top-right corner, click Add → Add custom connector.
  3. Enter a name (e.g. “Clara MX”) and the MCP server URL for your country.
  4. Click Add, then Connect — you’ll be redirected to the Clara login screen.
  5. Complete the login with your Clara account.
Once connected, Claude will list clara-mcp among its available tools.

Existing Users / Migration

If you had Clara MCP configured with the previous token-based setup: Claude Desktop — instead of supergateway, use mcp-remote, which supports the OAuth flow:
Restart Claude Desktop completely (File → Quit, not just close the window). On reopening, a login window will open automatically — complete it with your Clara account.
This config file no longer stores any credentials — there’s no token to protect. Authentication happens through the login window, not the config file.
Claude Web — remove your previous connector configuration and follow the New Users steps above.

Test It

Ask Claude something like:
  • “List my Clara cards”
  • “Show my last 10 transactions”
  • “Lock the card ending in 3540”
Claude will connect to Clara in real time and respond.

Option B — Claude Code (CLI)

New Users

  1. In a terminal (outside Claude Code), run:
  1. Open Claude Code and run /mcp to select the Clara MCP server.
  2. Select Authenticate — you’ll be redirected to the OAuth login flow. Complete it with your Clara account.

Existing Users / Migration

The previous token header is no longer recognized by the new MCP server. Follow the New Users steps above to reconnect — you’ll need to log in again.

Option C — ChatGPT

Enable Custom Connectors

  1. Go to Profile → Settings → Security & Login.
  2. Turn on Developer Mode.

Add Clara MCP

  1. Go to Plugins and click the + button in the top-right corner.
  2. Enter:
    • Name: “Clara MX” (or “Clara CO”, “Clara BR”) — this is just a label.
    • Connection: the MCP server URL for your country.
    • Authentication: OAuth.
  3. Click Create. A modal will appear — click Log in with Clara MX, which redirects you to the OAuth login flow.
  4. Complete the login with your Clara account.

Option D — Other MCP-Compatible Tools (Gemini, etc.)

Clara MCP uses the standard MCP protocol with OAuth authentication, so it works with any compatible tool that supports remote MCP connectors:
  1. Find the “Connectors” or “Integrations” section in your tool.
  2. Add a new custom connector.
  3. Enter the MCP server URL for your country.
  4. Complete the OAuth login flow when prompted.
If you run into issues with a specific tool, contact support.

Managing Multiple Companies

If you have access to more than one company in Clara, connecting logs you into the last company you used on web/mobile. To switch companies within the same conversation, just ask your assistant:
  • “What companies do I have access to?”
  • “Switch to [company name]“

Verify Your Connection

Once configured in any tool, test by asking:
“List my Clara cards”
If you see a list of cards from your company account, you’re connected correctly.

Troubleshooting

Asked to log in again
  • Your session expired — this is normal, just re-authenticate.
“No tools found” or Clara MCP doesn’t appear
  • Make sure you fully restarted the AI tool after connecting (quit and reopen, not just refresh).
  • Confirm that npx is available in your terminal (Claude Desktop config-file setup only).
Had Clara MCP connected before and it stopped working
  • The previous static-token method is no longer valid. Follow the migration steps for your tool above to reconnect via OAuth.
“Connection refused” or server unreachable
  • Check your internet connection.
  • The Clara MCP server may be temporarily unavailable — try again in a few minutes.
Lock/unlock returns a simple “Ok” message
  • This is a known Beta limitation. The operation executed correctly even if the response looks plain. The card was locked/unlocked successfully.
Transaction count shows 0
  • Known Beta issue with the summary counter. Actual transactions are returned correctly in the list.

Access & Security

  • There’s no separate token to generate, store, or lose — your MCP access is tied to your Clara login session.
  • There’s no self-service revocation yet — to revoke access for a connected AI tool, request it via Customer Happiness (in-platform chat or contacto@clara.com) or the Solution Engineering team. Access is cut off immediately across all connected tools.