---
title: "Connect Claude Code"
description: "Add the Monitive MCP server to Claude Code with one shell command."
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

- Claude Code installed (current stable)
- A Monitive account (sign in with GitHub at [my.monitive.com](https://my.monitive.com))
- (Only for the API-key alternative below) an `mk_live_` key — see [API keys](/docs/api-keys/)

## Connect

Add the Monitive remote HTTP MCP server:

```bash
claude mcp add --transport http monitive https://api.monitive.com/mcp
```

Then in Claude Code run `/mcp` — Claude Code opens your browser to authorize via GitHub and stores the access token automatically. No key to manage or paste.

### Alternative: API key CI / headless / automation

Use this in non-interactive environments where a browser OAuth flow isn't possible. The same `mk_live_` key also powers the REST API and the `assert-healthy` GitHub Action.

```bash
claude mcp add --transport http monitive https://api.monitive.com/mcp \
  --header "Authorization: Bearer mk_live_..."
```

Replace `mk_live_...` with your actual API key.

## Verify

In Claude Code, type `/mcp` and confirm `monitive` appears with status **connected**. Then ask:

> list my monitors

You should see a tool call to `list_monitors` and a list of your monitors (or an empty result if you don't have any yet).

## Common errors

| Symptom | Cause | Fix |
|---------|-------|-----|
| `401 Unauthorized` (API-key method) | Key is wrong, missing, or not `mk_live_`-prefixed | Confirm the key from [API keys](/docs/api-keys/#api-key-format) starts with `mk_live_` and is pasted in full |
| Browser didn't open / auth didn't finish | OAuth flow was interrupted | Re-run `/mcp` in Claude Code; it re-initiates the OAuth flow |
| Tools missing after `/mcp` | MCP server registered but Claude Code hasn't reloaded | Restart Claude Code fully |
| Connection refused / DNS error | Wrong host in the server URL | The endpoint is `https://api.monitive.com/mcp`, not the marketing host |

## See also

- [MCP reference and host compatibility matrix](/docs/mcp/)
- [Connect ChatGPT](/docs/connect-chatgpt/)
- [Connect Cursor](/docs/connect-cursor/)
- [Connect via OpenAI API](/docs/connect-openai-api/)
- [Connect via REST API](/docs/connect-rest-api/)