# MCP & IDE Integrations

Configure one-click MCP setup for Cursor and Claude Code, plus usage patterns and token scope guidance.

<!-- docs-source -->
Source: https://learning.monetizekit.app/docs/tools/mcp-ide
<!-- /docs-source -->

### MCP Server

Endpoint: `{MONETIZEKIT_MCP_SERVER_URL}` (JSON-RPC MCP endpoint; for the in-app adapter use `https://your-domain/api/mcp`).

Recommended read-only MCP permissions: `catalog:view`, `customers:read`, `entitlements:read`, `usage:read`, `integrations:view`, `observability:view`, `audit:view` — see the [Authentication guide](/docs/getting-started/authentication) for how scoped keys and service tokens work more generally.

Use elevated scopes only for managed write workflows and rotate keys regularly.

```bash
monetizekit auth service-token create docs-mcp --scopes catalog:view,customers:read,entitlements:read,usage:read,integrations:view,observability:view,audit:view --ttl 30d
```

```json
{
  "mcpServers": {
    "monetizekit-mcp": {
      "url": "https://app.monetizekit.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${MONETIZEKIT_MCP_TOKEN}"
      },
      "env": {
        "MONETIZEKIT_MCP_TOKEN": "${MONETIZEKIT_MCP_TOKEN}"
      }
    }
  }
}
```

### Cursor IDE

Use `.cursor/mcp.json` template or run `monetizekit init --cursor`. Reference: `docs/cursor/installation.md` and `docs/cursor/security.md`.

### Claude Code + Skill Pack

Import the `monetizekit-claude-skill-pack` bundle and configure MCP connector URL + scoped token. Reference files: `monetizekit-claude-skill-pack/manifest.json`, `monetizekit-claude-skill-pack/docs/installation.md`.

```bash
claude mcp add monetizekit-mcp https://app.monetizekit.app/api/mcp --header "Authorization: Bearer ${MONETIZEKIT_MCP_TOKEN}"
```

### Usage quick start

After installation, ensure your token includes `observability:view`, then ask your assistant to call `docs.get_manifest` first and `docs.get_section` for grounded answers.

```bash
Prompt: "Run tools/list, then docs.get_manifest, then docs.get_section { section: \"openapi\" }, and cite endpoint paths in your answer."
```