Skip to main content

​
Prerequisites

  • Claude Desktop installed
  • A RevyOps API key — get one from Settings → API Keys

​
Setup

1

Open Claude Desktop config

Find the config file for your operating system:macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Windows:
%APPDATA%\Claude\claude_desktop_config.json
Create the file if it doesn’t exist.
2

Add the RevyOps server

Add the following JSON (merge with any existing MCP servers you have):
{
  "mcpServers": {
    "revyops": {
      "type": "http",
      "url": "https://mcp.revyops.com/mcp",
      "headers": {
        "X-API-KEY": "RO-your-api-key-here"
      }
    }
  }
}
Replace RO-your-api-key-here with your actual API key.
3

Restart Claude Desktop

Quit and reopen Claude Desktop. The RevyOps tools will appear automatically in the tools panel.
4

Verify the connection

In a new conversation, ask:
“List my RevyOps clients”
Claude should respond with your available workspace(s).

​
Multiple Workspaces

If you manage multiple client workspaces, add a separate server entry per API key: 
{
  "mcpServers": {
    "revyops-client-a": {
      "type": "http",
      "url": "https://mcp.revyops.com/mcp",
      "headers": { "X-API-KEY": "RO-key-for-client-a" }
    },
    "revyops-client-b": {
      "type": "http",
      "url": "https://mcp.revyops.com/mcp",
      "headers": { "X-API-KEY": "RO-key-for-client-b" }
    }
  }
}
Or pass a comma-separated list of keys in a single entry: 
{
  "mcpServers": {
    "revyops": {
      "type": "http",
      "url": "https://mcp.revyops.com/mcp",
      "headers": {
        "X-API-KEY": "RO-key-for-client-a,RO-key-for-client-b"
      }
    }
  }
}
Use list_clients to see all resolved workspaces, then reference them by name in your prompts.

​
Troubleshooting

Make sure you fully quit Claude Desktop (not just closed the window) and reopened it. On macOS, right-click the Dock icon and select Quit.
Double-check your API key in RevyOps → Settings → API Keys. Keys must start with RO-.
Verify your internet connection and that https://mcp.revyops.com is reachable. If you’re self-hosting, check that your MCP server is running and the URL is correct.