# Connect Claude

Canonical URL: https://support.optimonk.com/en/articles/connect-claude

# Connect Claude

Claude on the web, desktop, and Claude Code.

Claude connects over remote MCP with OAuth. There is no key to create and nothing to paste but the URL.

**MCP endpoint**

```
https://agentic.optimonk.com/mcp
```

## Claude Code

Add the server from your terminal:

```
claude mcp add --transport http optimonk https://agentic.optimonk.com/mcp
```

In Claude Code, run `/mcp`, select `optimonk`, and follow the authentication steps in your browser. With Claude Code v2.1.186 or later, you can also run `claude mcp login optimonk` from your terminal. See the [official OAuth instructions](https://code.claude.com/docs/en/mcp#authenticate-with-remote-mcp-servers).

## Claude on the web and desktop

Add a custom connector named OptiMonk with the endpoint above. Claude currently documents `Customize → Connectors`, then the plus button and `Add custom connector`. Leave the optional OAuth client ID and secret unset, then add the connector and complete its connection and consent flow.

Enable OptiMonk for your conversation using the chat’s plus menu and `Connectors`. On Team and Enterprise plans, an owner must add the connector first. If the controls differ or are unavailable, follow Claude’s [current custom-connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for your plan.

## What you should see

For OAuth, complete your client’s authentication flow, then approve the requested OptiMonk permissions. See [Authentication & access](/en/articles/authentication-and-access) for consent-screen details and connection management.

## Check it worked

Ask your agent to call `whoami`. It answers with the account it is acting as and the permissions it holds, which is also the first thing to check if a later call says something is missing.

## If it does not connect

- **Nothing happens after adding the URL.** Complete your client’s authentication step first. If the consent tab is blocked, allow pop-ups for this site and retry.

- **You were asked for a key or token.** OAuth connections do not require an API key. If your client does not support OAuth or its callback is not allowed, use a Bearer API key instead — see [Authentication & access](/en/articles/authentication-and-access).

- **Connected, but calls fail.** Call `whoami` first: a credential on the wrong account fails exactly like a missing object.