# Connect Cursor

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

Configure mcp.json and authenticate in Cursor.

Cursor speaks remote MCP over HTTP. Add the endpoint and approve the connection in your browser.

**MCP endpoint**

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

## Configure Cursor desktop

1. **Add the configuration file**

Create `.cursor/mcp.json` in your project root, or use `~/.cursor/mcp.json` for all projects. If the file already exists, add the `optimonk` entry to its existing `mcpServers` object, preserving your other servers.

```json
{ "mcpServers": { "optimonk": { "url": "https://agentic.optimonk.com/mcp" } } }
```
2. **Authenticate and enable the server**

Complete Cursor’s OAuth sign-in for `optimonk` and approve the requested permissions in your browser. No API key or static OAuth credentials are needed for this configuration. Cursor documents server management and enablement under `Customize` in the sidebar.

If the authentication controls differ in your version, follow the [official Cursor MCP guide](https://cursor.com/docs/mcp). The configuration file above is the documented custom-server setup.

## 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.