Connect Claude or Codex

Cloudpepper’s MCP server lives at https://mcp.cloudpepper.io. To connect, you add that URL in your client and sign in with your Cloudpepper account.

There is nothing else to create. No OAuth client ID, no client secret, no API key. Cloudpepper registers your client for you, so the only value you ever paste is the server URL. An API key is available as an alternative for machine clients and automation, covered at the end.

claude.ai and Claude Desktop

1. Open Settings → Connectors. On a Team or Enterprise plan, an owner adds it once under Organization settings → Connectors, then each member connects.
2. Click Add custom connector.
3. Enter the server URL https://mcp.cloudpepper.io. Leave Advanced settings empty. You do not need an OAuth Client ID or Secret.
4. Click Add, then Connect. A Cloudpepper sign-in page opens. Sign in, pick the account the assistant should act on, and approve.

The tools appear in Claude once you approve.

Note

The connector dialog has no field for an API key or bearer token. That is by design: claude.ai connects over a browser sign-in only. To use an API key, use Claude Code or Codex below.

Claude Code

Add the server over HTTP, then authenticate in a session:

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

Start Claude Code, run /mcp, select cloudpepper, and choose Authenticate. Your browser opens the Cloudpepper sign-in. Approve it, and the tools are ready. Claude Code stores and refreshes the token for you.

Check the status any time with:

claude mcp list

Codex

Codex’s support for remote MCP servers is newer and still marked experimental, so it takes one extra setting. In ~/.codex/config.toml:

[features]
rmcp_client = true

[mcp_servers.cloudpepper]
url = "https://mcp.cloudpepper.io"

(rmcp_client was previously named experimental_use_rmcp_client; the old name still works on current versions.)

Then sign in:

codex mcp login cloudpepper

Your browser opens the Cloudpepper sign-in. Approve it, and Codex stores the token. Confirm with codex mcp list. Codex moves quickly, so check its own docs if a flag name has shifted.

Connect with an API key

For automation, CI, or a client that cannot open a browser, use a Cloudpepper API key instead of signing in. API keys are an Agency feature. On Pro, connect by signing in, which is the recommended path anyway.

Create the key in your dashboard under Settings, then:

• Claude Code: pass it as a header.

  claude mcp add --transport http cloudpepper https://mcp.cloudpepper.io \
    --header "Authorization: Bearer aak-your-key-here"

• Codex: keep the key in an environment variable and reference it by name.

  [mcp_servers.cloudpepper]
  url = "https://mcp.cloudpepper.io"
  bearer_token_env_var = "CLOUDPEPPER_MCP_TOKEN"

  Then export CLOUDPEPPER_MCP_TOKEN=aak-your-key-here before you start Codex.

claude.ai and Claude Desktop do not accept a pasted key. Use the browser sign-in there.

Plans

MCP access is available on Pro and Agency. Signing in with your account works on both. API keys are Agency only.

Your first request

Ask your assistant to list your servers, or to find your slowest query. See Find and fix slow Odoo queries for a worked example.

Troubleshooting

• It asks for an OAuth Client ID or Secret. Leave those blank. Cloudpepper registers the client for you. If a client will not proceed without them, it may be out of date. Update it and try again.
• Connected, but no tools listed. Your plan may not include MCP. Account sign-in on Pro or Agency gives you the full read and write set. If you just upgraded, reconnect the client so it reloads the tool list.
• The sign-in page did not open. Check the URL is exactly https://mcp.cloudpepper.io, with no path after it.
• It acted as the wrong account. Disconnect, reconnect, and pick the right account on the chooser screen.