API Key clients (Cursor, Claude Code, Claude Desktop)

Use this guide if your MCP client doesn’t have a built-in custom connector UI (Claude AI and ChatGPT do — see their dedicated pages). Programmatic clients connect with an ApiKey token sent on the standard Authorization header.

Client capabilities

• Resources

• Resource templates

• Tools

• Prompts

• Completion

The server speaks Streamable HTTP over a single endpoint (POST https://web.omniconvert.com/mcp, JSON-RPC 2.0). Clients that only support stdio need a local bridge — see the Claude Desktop section below.

How to obtain an ApiKey

1. Log into the Omniconvert dashboard.

2. Open the website dropdown in the top navbar and click API credentials.

3. Switch to the MCP server tab.

4. Click Generate MCP server Api Key.

5. Copy and store the token securely — treat it as a secret.

Each user can generate multiple tokens. Tokens are scoped to your account; they cannot reach resources owned by a different account.

Auth header

Authorization: ApiKey <your-token>

Use the literal word ApiKey (not Bearer, not X-Api-Key). No other headers are required.

Cursor (and any client with native Streamable HTTP support)

Add the server to your MCP config (~/.cursor/mcp.json for global, or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "omniconvert": {
      "url": "https://web.omniconvert.com/mcp",
      "headers": {
        "Authorization": "ApiKey <your-token>"
      }
    }
  }
}

Reload Cursor; the omniconvert server should appear under MCP servers as connected, and its tools become available to the agent.

Claude Code (CLI)

One-liner to register the server at user scope (so it’s available across projects):

claude mcp add --transport http --scope user omniconvert https://web.omniconvert.com/mcp \
  --header "Authorization: ApiKey <your-token>"

Verify with:

claude mcp list

You should see:

omniconvert: https://web.omniconvert.com/mcp (HTTP) - ✓ Connected

To remove later: claude mcp remove –scope user omniconvert

Claude Desktop (stdio — needs a bridge)

Claude Desktop currently speaks stdio only, so use the mcp-remote bridge to translate to Streamable HTTP. Edit claude_desktop_config.json:

{
  "mcpServers": {
    "omniconvert": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://web.omniconvert.com/mcp",
        "--header",
        "Authorization: ApiKey <your-token>"
      ]
    }
  }
}

Restart Claude Desktop. The server appears under MCP tools after the bridge connects.

Verifying the connection

Once connected, ask the agent something concrete that exercises a tool, for example:

List my Omniconvert websites and their active experiments.

The client should call init first, then list_experiments per website. If the agent reports an auth error, double-check the header value — the most common mistake is using Bearer or X-Api-Key instead of ApiKey.

The token is sent on every request. If you rotate or revoke it in the dashboard, update each client config.