> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revyops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Other Agents

> Connect any MCP-compatible agent app to RevyOps.

RevyOps works with any agent app that supports the Model Context Protocol. You need two things:

| Setting    | Value                         |
| ---------- | ----------------------------- |
| Server URL | `https://mcp.revyops.com/mcp` |
| Header     | `X-API-KEY: RO-your-key-here` |

Get a key from the **Keys** tab on the **Developer** page. See [Authentication](/api-reference/authentication).

## If your app supports remote servers with headers

Add a remote (HTTP) MCP server, set the URL above, and add an `X-API-KEY` header with your key. Then restart the app.

## If your app only runs local commands

Some apps can only start MCP servers as a local command. Use `mcp-remote` to bridge to RevyOps. This needs [Node.js](https://nodejs.org) installed.

```json theme={null}
{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.revyops.com/mcp",
    "--header",
    "X-API-KEY: RO-your-key-here"
  ]
}
```

Put this wherever your app lists its MCP servers, then restart the app.

## Check the connection

Ask your agent to *"list my RevyOps clients"*. It should reply with the workspaces your key can access.

## Managing multiple clients

Comma-separate your keys in the header: `X-API-KEY: RO-key1, RO-key2, RO-key3`. The agent routes each question to the right workspace.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Server disconnected on startup">
    Double-check your API key is copied correctly with no extra spaces.
  </Accordion>

  <Accordion title="&#x22;Client not found&#x22; error">
    Ask your agent to "list my clients" first. This confirms which workspaces your key has access to.
  </Accordion>

  <Accordion title="Need a new API key">
    Go to **Developer → Keys → Generate key**.
  </Accordion>
</AccordionGroup>