URL: /docs/mcp/install/cursor

---
title: Cursor
description: Connect the Revised MCP server to Cursor via mcp.json, over OAuth or with an API key.
---

The endpoint is `https://getrevised.com/api/mcp`. Edit `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` in a project.

<Tabs>
  <Tab title="OAuth">
```json
{
  "mcpServers": {
    "revised": {
      "url": "https://getrevised.com/api/mcp"
    }
  }
}
```

Restart Cursor, open **Settings → MCP**, and click **Needs login** on the `revised` entry. A browser tab opens on the Revised sign-in; accept the consent screen and the entry turns green with the tool count.
  </Tab>
  <Tab title="API key">
```json
{
  "mcpServers": {
    "revised": {
      "url": "https://getrevised.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rvd_yourprefix_yoursecret"
      }
    }
  }
}
```

Create the key at [getrevised.com/account](https://getrevised.com/account) — free on every plan. Restart Cursor; the entry should come up connected without a login step.
  </Tab>
</Tabs>

## Verify

Open **Settings → MCP**. The `revised` server should show green with nine tools. Then ask in chat:

> What plan am I on with Revised?

Cursor should call `whoami` and report the plan, the reveals left this month and the rate limit.

## Notes

- A project-level `.cursor/mcp.json` checked into a repository is the wrong place for an API key. Use OAuth, or put the key in the global `~/.cursor/mcp.json`.
- `reveal_domain` is the only tool that can spend. See [Tools](/docs/mcp/tools#reveal_domain).
- MCP calls and REST calls share one per-minute counter per key. See [Rate limits](/docs/api/rate-limits).