Connect Revised to Claude.ai and Claude Desktop

The endpoint is https://getrevised.com/api/mcp.

Custom connector (recommended)

The same connector serves claude.ai and the desktop app: add it once and it appears in both. Where custom connectors are available depends on your Claude plan; if Add custom connector is missing, check your plan, or on a Team or Enterprise plan ask an owner to enable it.

1. Open the connector settings

   In claude.ai or the desktop app, open Settings → Connectors.

2. Add a custom connector

   Choose Add custom connector, name it Revised and paste https://getrevised.com/api/mcp. Leave the advanced OAuth fields empty: no header, no client id, no key.

3. Sign in

   Connect opens a browser tab on the Revised sign-in. Sign in and accept the consent screen. Claude stores the token and refreshes it on its own.

4. Verify

   In a new chat, enable the connector from the tools menu and ask: “What plan am I on with Revised?” Claude should call whoami and report the plan, your reveal position and the rate limit.

API key, through a local bridge

A custom connector is OAuth only, and claude_desktop_config.json launches local processes rather than connecting to a URL. To use a key (CI, a machine where you cannot sign in), run the mcp-remote bridge, which connects to the URL and adds the header. It needs Node.js for npx.

Create a key at getrevised.com/account, then edit the desktop app’s configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "revised": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://getrevised.com/api/mcp",
        "--header",
        "Authorization:${REVISED_AUTH}"
      ],
      "env": {
        "REVISED_AUTH": "Bearer rvd_yourprefix_yoursecret"
      }
    }
  }
}

Restart the app after saving. The header value goes through an environment variable because the bridge mishandles a space inside an argument on Windows.

Notes

• Seventeen tools are exposed. reveal_domain spends a reveal and run_deep_check spends credits; nothing else spends, and a reveal grant is permanent; see Tools.
• The reveal position and the hold cap are the account’s, not the connector’s. An assistant is bound by exactly the same limits you are.
• Holds are account-scoped: a hold taken through this connector is visible to, and releasable from, every other key and session on the account.
• Claude Code has its own page, with a one-line command: Claude Code.