Set up the SEOFix MCP server by hand

The SEOFix MCP server is a remote Streamable HTTP server at https://mcp.seofix.ai/mcp. Add it to your agent with your API key in an Authorization: Bearer sk_... header. The quickest way is npx seofix connect; this page covers doing it by hand.

#Before you start

You need an API key. In the app: Settings → Agent & MCP → Create API key. Copy it from the dialog: it is shown only once. The key acts for the team you were viewing when you created it. See API keys.

In the examples below, replace sk_... with your key.

#Claude Code

Run in your project's terminal:

claude mcp add --transport http seofix https://mcp.seofix.ai/mcp \
  --header "Authorization: Bearer sk_..."

Add --scope user to use it in every project, not only this one. Check it with claude mcp get seofix.

#Codex

Add to ~/.codex/config.toml:

[mcp_servers.seofix]
url = "https://mcp.seofix.ai/mcp"
http_headers = { "Authorization" = "Bearer sk_..." }

To keep the key out of the file, use bearer_token_env_var = "SEOFIX_API_KEY" instead of http_headers, and set SEOFIX_API_KEY in the environment Codex runs in.

#Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "seofix": {
      "url": "https://mcp.seofix.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

This file holds your key. Keep it out of version control, for example by adding /.cursor/mcp.json to .git/info/exclude or .gitignore.

#Other MCP clients

Any client that supports remote HTTP servers with custom headers works. The generic shape is:

{
  "mcpServers": {
    "seofix": {
      "type": "http",
      "url": "https://mcp.seofix.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

Key names differ between clients; check your client's documentation. If your client only supports local stdio servers, put an HTTP-to-stdio bridge in front of the URL. The server itself only speaks Streamable HTTP.

#How the server works

The server holds no credentials. It reads the bearer token from each request and passes it to the SEOFix REST API (https://api.seofix.ai/v1). Every tool call is therefore subject to the same permissions, credit costs and rate limits as the API: 60 requests per minute per key, plus per-endpoint limits. See Errors and rate limits.

#Tool results and errors

A successful tool returns one text item, usually compact JSON. get_fix_prompt returns markdown.

A failed tool returns a text item with isError: true in the form code: message, for example:

site_not_verified: Rechecks need a verified site. Verify ownership first: see GET /v1/sites/{id}/verification.

budget_exhausted errors also carry (resets_at: <ISO time>). The codes are the API's error codes; see Errors and rate limits.

#Troubleshooting

To test your key without MCP:

curl -s https://api.seofix.ai/v1/ping -H "Authorization: Bearer $SEOFIX_API_KEY"

A valid key answers {"user_id": ...}.

#Related

• Connect your agent with npx seofix connect
• MCP tools reference
• Agent playbook
• API keys