Skip to main content

Connect a client

The server speaks the MCP Streamable HTTP transport at https://mcp.profundis.io. Pick your client below. First read Authentication: one-click OAuth is the simplest path (nothing to copy or store), with a Profundis API key as the option for scripts and headless clients.

note

You need an active subscription or credit pack to connect — the same entitlement as the API. A Free account with only its monthly credit allocation can't use the MCP. See Who can connect.

Claude Code​

No key to copy. Add the server with no header, then authenticate:

claude mcp add --transport http profundis https://mcp.profundis.io

In Claude Code, run /mcp, select profundis, and choose Authenticate. Your browser opens to sign in to Profundis; the token is stored and refreshed for you (nothing to paste or store). Then:

claude mcp list               # profundis should show as connected
claude mcp remove profundis   # to remove it

API key instead (scripts / CI)​

If you prefer a static key for a headless or automated setup, pass it as a bearer header:

claude mcp add --transport http profundis https://mcp.profundis.io \
  --header "Authorization: Bearer <YOUR_API_KEY>"

Add --scope project to share the server with your team via a checked-in .mcp.json, or --scope user to make it available across all your projects. The default is local (just you, just this project).

Config file (.mcp.json)​

Equivalently (the API-key path), add the server to a .mcp.json at your project root (the file --scope project writes, meant to be committed):

{
  "mcpServers": {
    "profundis": {
      "type": "http",
      "url": "https://mcp.profundis.io",
      "headers": {
        "Authorization": "Bearer ${PROFUNDIS_API_KEY}"
      }
    }
  }
}

Claude Code expands environment variables in .mcp.json (${VAR}, or ${VAR:-default}), so reference ${PROFUNDIS_API_KEY} rather than pasting the key. Do not commit a raw key. Local- and user-scoped servers live in ~/.claude.json instead of the project .mcp.json. (One-click OAuth above needs none of this.)

VS Code (Claude Code extension)​

The Claude Code VS Code extension reads the same config as the terminal: the project .mcp.json and ~/.claude.json. There is no separate VS Code file for it.

  1. Open the integrated terminal (Ctrl+` / Cmd+`) and run the same claude mcp add command as above, or edit .mcp.json directly.
  2. In the Claude chat panel, type /mcp to see and manage configured servers: reconnect, run the OAuth Authenticate step, or check status. (New servers are added via the CLI or .mcp.json, not from the panel.)

Claude and Claude Desktop​

Claude.ai and Claude Desktop connect to remote MCP servers as custom connectors with one-click OAuth, so there is no key to copy.

  1. Open Settings → Connectors and choose Add custom connector.
  2. Enter the URL https://mcp.profundis.io.
  3. Save, then click Connect. You are redirected to sign in to Profundis (Google sign-in) and approve the connection.
  4. Once connected, the Profundis tools are available in your chats.

Custom connectors require a Claude plan that supports them. You can disconnect from the same Connectors screen, and revoke the connection from your Profundis profile.

ChatGPT​

ChatGPT connects to remote MCP servers as a connector, also with one-click OAuth.

  1. Open Settings → Connectors and add a connector by URL.
  2. Enter https://mcp.profundis.io.
  3. Authorize: you are redirected to sign in to Profundis and approve the connection.
  4. Enable the connector for your conversation (for example, in a chat or a Deep Research run) so ChatGPT can call the Profundis tools.

Connector availability depends on your ChatGPT plan and workspace settings. Revoke access from your Profundis profile at any time.

Other MCP clients​

Any client that supports the MCP Streamable HTTP transport can connect:

  • Endpoint: https://mcp.profundis.io
  • Transport: Streamable HTTP
  • Auth: complete the OAuth flow if your client supports remote authorization (the server publishes protected-resource metadata at /.well-known/oauth-protected-resource); otherwise send Authorization: Bearer <YOUR_API_KEY>.

After connecting, list the tools to confirm. You should see the nine tools described in the Tools reference.

tip

If a tool call returns an "unauthorized" error, your credential is missing or not valid for this environment. Check that you used a current API key from your profile and that your account has an active plan or credits.

Last updated on