# Cursor

# Connect Cursor

[Cursor](https://cursor.com) connects to remote MCP servers through an `mcp.json` file.

New to Monad's MCP server? Start with the [MCP overview](/mcp/index).

## Prerequisites

- Cursor installed
- A Monad account belonging to at least one organization
- MCP access enabled for your user — see [Access](/mcp/index#access)

## 1. Add the server

Create or edit **`~/.cursor/mcp.json`** to make Monad available in every project:

```json
{
  "mcpServers": {
    "monad": {
      "url": "https://app.monad.com/mcp"
    }
  }
}
```

To scope it to one project instead, put the same JSON in **`.cursor/mcp.json`** at the project root. That file can be committed, so collaborators pick up the server automatically — each still authenticates as themselves.

No client id or secret goes in this file. Monad's authorization server supports dynamic client registration, so Cursor registers itself and runs the OAuth flow on first use.

## 2. Authorize

Open **Settings → MCP**. Monad appears in the list; start the connection and Cursor opens your browser to Monad's consent screen.

Approve it, and the tools become available to the agent.

## 3. Verify

In the agent, ask for something read-only:

> List my Monad pipelines

If it returns your pipelines, the connection is live.

## Next: Using It

You are connected. For what you can do through the MCP, example requests, and the habits that get good results, see **[Using the MCP](/guides/mcp-usage)**.

## Managing the Connection

Enable, disable and inspect the server under **Settings → MCP**.

To disconnect properly, revoke the client under **Settings → Connected Applications** in the Monad UI — that takes effect immediately — and remove the entry from `mcp.json`.

## Troubleshooting

**Monad does not appear in Settings → MCP.**
Check the JSON parses and is in the right place: `~/.cursor/mcp.json` for global, `.cursor/mcp.json` at the project root for project scope. Reload Cursor after editing.

**The connect action does not open a browser.**
Cursor's OAuth handling for remote servers has been uneven across releases. Update to the latest version and retry. If it still does not open, the [Cursor community forum](https://forum.cursor.com) is the fastest place to check for a known issue with your build.

For anything not specific to Cursor — refused requests, missing organizations, writes being denied — see [Troubleshooting](/mcp/index#troubleshooting) on the overview page.