Install REVOR AI MCP with an AI assistant

This is the canonical installation guide for AI assistants, automated installers, and users. REVOR AI MCP uses API key authentication, and the client must support custom headers. Prefer a Secret store; a private local configuration with restricted file access is also acceptable on a single-user device.

Required installation information

If the client supports neither a Secret store nor a local header configuration readable only by the current user, use REVOR AI browser OAuth if the client supports remote MCP OAuth. Otherwise, use a different MCP client.

Ready-to-use JSON configuration

Clients that expose an mcp.json file or JSON editor can merge this server entry into the existing mcpServers object:

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
    }
  }
}

This is a remote Streamable HTTP configuration. It requires no command, args, npx, proxy package, or local process. An installation agent must follow these rules:

1. Read the existing client configuration first and merge the revor-ai entry without replacing other mcpServers.
2. Prefer the client's Secret input or secret-reference feature. Do not write a plaintext key into JSON when secure storage is available.
3. If the client only supports a private local JSON file, the user may enter the real key in that local field. The file must be readable only by the current user and must not live in source control, a shared directory, or a cloud-synchronized directory. Never ask the user to send the key in chat.
4. After the user enters the real key locally, never echo the complete configuration, create a screenshot containing the key, or copy it into chat, logs, or source control.
5. Do not invent environment-variable syntax such as ${REVOR_API_KEY} unless the client's official format explicitly supports it.
6. Save or enable the entry, reload the tool list, and restart the client only if needed. Do not report success until revor_whoami succeeds.

Some clients use a different top-level field or a separate Secret UI. Preserve the same URL and x-api-key header while following that client's native configuration format instead of forcing incompatible JSON.

Instructions for an AI installation assistant

Send this entire block to an AI assistant that can manage MCP settings:

TextCopy
Install REVOR AI MCP and follow these requirements exactly:

1. Use the client's built-in Add remote MCP, Connector, or equivalent feature.
2. Set the name to REVOR AI and the server URL to https://revor.ai/api/mcp.
3. This is a remote MCP service. Do not download an npm package or run npx, pnpm, Docker, or a local server.
4. Use API key authentication by default. If the user has no key, direct them to https://revor.ai/my-api-keys. Configure the key as x-api-key; Authorization: Bearer sk-revor-... is also accepted when the client only supports an Authorization header.
5. If the client lets the assistant open or generate a private Secret input, present it and ask the user to enter the key there. Never ask for or accept an API key in chat. If only a private local configuration exists on a single-user device, have the user enter the key locally and restrict file access. Never store a plaintext key in shared, hosted, or synchronized configuration.
6. For an mcp.json client, merge the revor-ai entry into the existing mcpServers object without replacing other services. Use the JSON structure on this page instead of searching for an npm package or guessing a launch command.
7. If the assistant cannot enter the key through a Secret, write only the placeholder and tell the user which local field to fill. Never request the key in chat or echo a configuration after a real key has been inserted.
8. Save and enable the connection, reload tools, and call revor_whoami. Report installation as complete only after that call succeeds and the REVOR AI tools are visible.
9. Use browser OAuth only when the client cannot safely store a custom header. If both OAuth and an API key are configured, the API key takes precedence.

Connect with an API key

1. Create or select a REVOR AI API key on the API Keys page.
2. Open the client's secure custom-header or secret configuration.
3. Add the remote server URL https://revor.ai/api/mcp.
4. Add one of these headers:

TextCopy
x-api-key: sk-revor-...

Preferred; or, when the client only accepts an Authorization header:

TextCopy
Authorization: Bearer sk-revor-...

1. Save, connect, reload tools, and call revor_whoami.

For assisted installation, prefer a private Secret input. Without one, a private local configuration readable only by the current user is acceptable on a single-user device. Never request or accept the key in chat, and never put it in documentation, screenshots, source control, logs, shared configuration, or cloud-synchronized directories.

Configuration decision rules

• If secure custom headers are supported, prefer x-api-key.
• If only a secure Authorization header is supported, use Bearer sk-revor-....
• If no Secret exists but the single-user device supports a private local header configuration, connection is possible; restrict file access and do not synchronize or share it.
• If a custom header can only be stored in shared, hosted, or public configuration, use the client's browser OAuth flow instead of a plaintext key.
• If neither a private header nor browser OAuth is supported, this client version cannot connect securely to REVOR AI MCP.
• If both authentication methods are configured, the API key takes precedence.
• If the client accepts only command, args, or stdio, that client version cannot connect directly to REVOR AI Remote MCP.
• If a configuration file is required, follow that client's own format and reference the key through its supported secret/environment mechanism when possible.

Do not use a REST API URL, tool name, or another address as the MCP server URL.

Installation success criteria

Installation is complete only when:

1. The client reports that REVOR AI is connected.
2. The tool list matches the granular permissions granted to that API key. revor_whoami must be visible; business tools intentionally omitted by a restricted key need not appear.
3. revor_whoami succeeds and confirms the account and the granted granular MCP permissions.
4. A non-billable verification remains available after reconnecting the client.

Use this verification request:

TextCopy
Call revor_whoami to check the current REVOR AI MCP account and permissions, then list the available REVOR AI tools. Do not run a billable query.

Common errors and recovery

The server returns 401 without an API key

Create a key on the API Keys page, then configure x-api-key in the client's secure Header or Secret settings.

The server returns permission_denied

The API key does not have permission for that tool, or the account plan does not include the capability. Update the key permissions or use an appropriate key.

An old connection keeps using the wrong authentication

Some clients cache headers. Delete and recreate the connection, or explicitly remove the stale key before reconnecting.

API key lifetime

API keys remain usable until they expire or are revoked and can be independently restricted and rate-limited. Rotate a key if it may have been exposed.