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 or Secret settings.
• Make sure the client can access https://revor.ai.

You do not need to download a REVOR AI server. Connect with an API key and prefer a Secret store. On a single-user device, a private local configuration readable only by the current user is also acceptable, but it must remain outside source control, shared folders, and cloud sync.

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:

The client must support secure custom headers or Secret settings. If it only shows a Server URL field and cannot configure a header, it cannot connect to REVOR AI MCP. Do not append a tool path or credentials 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.

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 client has no Header or Secret setting

The client cannot securely configure a REVOR AI API key. Upgrade it or use a client that supports remote MCP and secure custom headers.

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 configuring the API key

Confirm that the header name is x-api-key and that the key is still valid, then reload tools or reconnect.

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

Replace the key with one owned by the intended account, reconnect, and call revor_whoami to verify the account.

Remove access

Delete the REVOR AI MCP service from the client. If the key was dedicated to that client, revoke it in REVOR AI as well. Removing only the client configuration does not revoke the key.