Technical details

This page is for developers connecting through a configuration file, and for anyone curious how the AI Integration works under the hood. For the standard, click-through setup, see Connect Claude.

The endpoint is:

https://mcp.reuzenpanda.app/mcp

Developer setup (config-file clients)

Some clients — the Claude desktop app via its config file and the Claude Code CLI — connect through a configuration file instead of the connector screen. Because the endpoint uses OAuth, these use the mcp-remote (opens in a new tab) helper, which opens a browser for you to sign in.

Claude desktop (`claude_desktop_config.json`)

{
  "mcpServers": {
    "reuzenpanda": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote@latest",
        "https://mcp.reuzenpanda.app/mcp",
        "--static-oauth-client-info", "{\"client_id\":\"claude\",\"client_secret\":\"claude\"}"
      ]
    }
  }
}

Restart Claude; a browser window opens the first time to complete the Reuzenpanda sign-in.

Claude Code (CLI)

claude mcp add reuzenpanda -- npx -y mcp-remote@latest https://mcp.reuzenpanda.app/mcp --static-oauth-client-info '{"client_id":"claude","client_secret":"claude"}'

Then run /mcp inside Claude Code to complete the browser sign-in.

About the OAuth client. claude / claude is the fixed Client ID and Secret that identifies the Claude app to Reuzenpanda — it's the same for everyone and passed via --static-oauth-client-info because the sign-in still happens with your own Reuzenpanda account in the browser.

How it works

A short overview of what's behind https://mcp.reuzenpanda.app/mcp:

One gateway, many services. The endpoint is an MCP gateway that fronts the individual Reuzenpanda backend services and exposes them as a single tool list. Tools are namespaced per service as <service>__<tool> (for example contact__getContactPerson or document__draftQuotationFromLead).
Transport. It speaks MCP over Streamable HTTP.
Authentication. Access is protected with OAuth 2.0 / OpenID Connect through the Reuzenpanda identity provider. Clients discover the sign-in flow automatically (RFC 9728 / 8414), which is why pasting the URL is usually enough. Your access token is scoped to your account, and each backend service enforces its own permissions on it.
Sessions. A connection is tied to the token captured when it starts. If your session expires mid-use, tool calls will fail — simply reconnect to refresh it.

Troubleshooting

ENOTDIR error with mcp-remote. If ~/.mcp-auth has become a file, remove it with rm -f ~/.mcp-auth and retry.
Session expired mid-use. Reconnect to obtain a fresh token; sessions are bound to the token captured when they start.
Still stuck? Reach out to support@reuzenpanda.nl.

Connect Claude Setup