Skip to main content

Before you start


Setup

1

Open the config file

In Claude Desktop, go to Settings → Developer → Edit Config, which opens claude_desktop_config.json.
2

Add the RevyOps server

Paste the following. If the file already lists other MCP servers, add revyops inside the existing mcpServers block.
Replace RO-your-key-here with your API key.
3

Restart Claude Desktop

Save the file, then fully quit and reopen Claude Desktop. On macOS, right-click the Dock icon and choose Quit. Closing the window isn’t enough.
4

Check the connection

In a new conversation, ask:
“List my RevyOps workspaces”
Claude should reply with the workspaces your key can access.

Managing multiple workspaces

Each workspace has its own API key. To use several in one Claude Desktop, comma-separate the keys in the header:
Ask Claude to “list my workspaces” to see which workspaces it can reach. If fewer workspaces come back than keys you pasted, RevyOps didn’t recognize one of them, most often because it’s a master key or was copied wrong. Then refer to a workspace by name in each question. A question that names no workspace goes to the workspace of the first key in the header.

Troubleshooting

Double-check your API key is copied correctly with no extra spaces, and that Node.js is installed.
Ask Claude to “list my workspaces” first, which confirms which workspaces your key has access to.
Make sure you fully quit Claude Desktop and reopened it after saving the config.
Go to Developer → Keys → Generate key. Workspace keys start with RV- (read-write) or RO- (read-only), and only these work with the MCP server. An agency master key, starting with ML-, is skipped without an error.