Connect an MCP client

This page explains how to add REVOR AI to an AI client that supports remote MCP.

Before you connect

• Have a REVOR AI account and an API key created on the API Keys page.
• Use a client that supports remote MCP and secure custom headers; if headers are unavailable, the client must support browser OAuth.
• Make sure the client can access https://revor.ai.

You do not need to download a REVOR AI server. API key authentication is the default installation method. Browser OAuth is only for clients that cannot securely store a header.

If an AI assistant is managing the setup, have it read the AI installation guide first. It must not infer MCP authentication from REST API documentation, Skill configuration, or old environment variables.

Add REVOR AI in a graphical client

Menu labels vary between clients, but the general flow is:

1. Create or select an API key on the API Keys page.
2. Open MCP, Tools, or Connectors in Settings and add a custom or remote MCP service.
3. Enter REVOR AI as the name.
4. Enter https://revor.ai/api/mcp as the server URL.
5. Enter x-api-key: sk-revor-... in the client's private Header or Secret settings.
6. Save and connect, then confirm that the tool list is available.
7. Call revor_whoami to verify the current account and permissions.

If the client asks for a connection type, choose Remote HTTP or Streamable HTTP.

Add REVOR AI in another client

Use the following details in any client that supports remote MCP:

If the client supports secure custom headers, use x-api-key. If it only shows a Server URL field, paste the URL directly and follow browser OAuth. Do not append a tool path or token to the URL.

There is no universal MCP client configuration-file format. Use the client's built-in MCP management or its documented format. Store API keys through its secret/environment feature whenever possible; never place a literal key in chat, prompts, or source control.

Clients with JSON configuration

When a client provides an mcp.json file or JSON editor, merge this entry into the existing configuration:

JSONCopy
{
  "mcpServers": {
    "revor-ai": {
      "url": "https://revor.ai/api/mcp",
      "headers": {
        "x-api-key": "<enter the REVOR AI API key privately on this device>"
      },
      "disabled": false
    }
  }
}

Do not replace existing mcpServers and do not add command or args. If the client provides a Secret field, store the key there instead of plaintext JSON. If only private local JSON is supported, have the user replace the placeholder locally. Never send the real key in chat or display the complete configuration after the key is present. Save and enable the service, reload tools, and call revor_whoami.

Compatibility option: Browser OAuth

Use this option only when the client cannot securely configure an API key header. Add the remote MCP and connect; the client should open the REVOR AI authorization page automatically. Do not construct an OAuth URL manually. The page shows the connecting client, your current REVOR AI account, and the access being requested.

Before allowing access, confirm that:

• You initiated the connection.
• The client name matches the application you are using.
• The browser address belongs to revor.ai.

After you select Allow access, the browser returns the authorization result to the client. Some clients show a short completion page; you can then close the tab and return to the client.

Verify the connection

Send this request in the client:

TextCopy
Use REVOR AI to check the connected account and list the available tools.

A working connection can call revor_whoami and expose the REVOR AI research, contact, and customs trade tools.

Troubleshooting

The sign-in page does not open

Confirm that the client supports browser authorization for remote MCP, then reconnect. Older clients that only support local command-based servers may not be able to connect directly.

If browser OAuth is unreliable but secure custom headers are available, configure x-api-key and reconnect.

The client asks for an API key or launch command

API Key is supported, but no local launch command is required. Configure the existing REVOR AI key as a secure x-api-key Header; never run npx, pnpm, Docker, or a local MCP server.

The client remains disconnected after authorization

Return to the client and refresh its tools or reconnect. If the browser already shows that authorization completed, start a fresh connection from the client instead of reopening an old authorization link.

Tools are visible but calls fail

Check your REVOR AI plan permissions, credit balance, and usage limits. Public tool errors indicate whether the issue is input, access, balance, rate limiting, or temporary job availability.

Change the connected account

For API key authentication, replace the key with one owned by the intended account. For OAuth, revoke the current client or remove the connection, then add it again and sign in with the intended account.

Remove access

Delete the REVOR AI MCP service from the client. Revoke an API key that was dedicated to that client, or revoke the OAuth authorization in REVOR AI account settings. Removing only the client configuration does not revoke the server-side credential.