---
title: "Connect Cursor"
description: "Add the Monitive MCP server to Cursor with OAuth or an API key."
doc_version: "1"
last_updated: "2026-11-19"
---

<!-- Cross-link contract: every "See also" block on all connect pages links to each other + /docs/mcp. Update in lock-step when adding a new connect page. -->

## Prerequisites

- Cursor stable release
- A Monitive account
- For API-key authentication, an `mk_live_` key from [my.monitive.com](https://my.monitive.com) — see [API keys](/docs/api-keys/)

## Connect

Create or open your Cursor MCP config file and add the Monitive server block:

- **Global (all projects):** `~/.cursor/mcp.json`
- **Project-local:** `./.cursor/mcp.json` in your project root

```json
{
  "mcpServers": {
    "monitive": {
      "url": "https://api.monitive.com/mcp",
      "headers": {
        "Authorization": "Bearer mk_live_..."
      }
    }
  }
}
```

Replace `mk_live_...` with your API key. Before you save a project-local configuration, add `.cursor/mcp.json` to `.gitignore`. Don't commit a live API key.

### OAuth alternative

Cursor supports OAuth for remote MCP servers that publish OAuth metadata. To use OAuth instead of an API key, omit the `headers` field:

```json
{
  "mcpServers": {
    "monitive": {
      "url": "https://api.monitive.com/mcp"
    }
  }
}
```

When Cursor prompts you, complete the browser flow to authorize your Monitive account.

## Verify

Close all Cursor windows and background processes, and then relaunch Cursor. Open the MCP panel and confirm that `monitive` appears as connected with eight tools.

To verify the integration end to end:

1. Ask Cursor to list your monitors:

   > List my monitors.

   Cursor calls `list_monitors` and returns your monitors or an empty result.

2. Ask Cursor to create a test monitor:

   > Create a monitor for `https://example.com/healthz` named `cursor-test`.

   Cursor calls `create_monitor` and returns a monitor with a `ref`. If a monitor for that URL already exists, the API returns `409 Conflict`. Delete the existing monitor or use a different URL.

3. Ask Cursor to delete the test monitor:

   > Delete the `cursor-test` monitor.

   Cursor calls `delete_monitor` and asks for confirmation because the tool has `destructiveHint: true`. Confirm the deletion. Monitive permanently deletes the monitor and its incident history.

## Common errors

| Symptom | Cause | Fix |
|---------|-------|-----|
| `401 Unauthorized` | Missing or incorrect key | Confirm the key starts with `mk_live_` and is pasted in full without extra whitespace |
| Server not appearing | Config file in wrong location | Cursor reads only `~/.cursor/mcp.json` or `./.cursor/mcp.json` |
| Tools not appearing after config change | Cursor not fully restarted | Quit Cursor fully (including background helper) and relaunch |
| Destructive tool blocked | Cursor is waiting for confirmation before it runs `delete_monitor` | Confirm the action in Cursor |
| `409 Conflict` on create | A monitor for that URL already exists | Delete the duplicate monitor by `ref`, or use a different URL |

## See also

- [MCP reference and host compatibility matrix](/docs/mcp/)
- [API keys](/docs/api-keys/)
- [API reference](/api-reference/)
- [Connect Claude Code](/docs/connect-claude-code/)
- [Connect ChatGPT](/docs/connect-chatgpt/)
- [Connect via OpenAI API](/docs/connect-openai-api/)
- [Connect via REST API](/docs/connect-rest-api/)