MCP Troubleshooting

Invalid API key

Check that the MCP client sends:

Authorization: Bearer aeo_live_...

The key must be active, well formed, and scoped to the workspace.

Plan capability required

The workspace plan must include API exports. The MCP server uses the same plan gate as the REST API.

No completed window

Many tools default to the latest completed measurement window. If no completed window exists, run tracking from the dashboard first and wait for answers to complete.

Rate limited

The default limit is 120 requests per minute per key. Wait before retrying or reduce repeated calls from the client.

Header issues

Some MCP clients require headers in a specific config object. Confirm that the key is sent as a header and not embedded in the URL.

Wrong endpoint

Use:

https://app.citlyze.com/api/mcp

Do not use /api/v1 as the MCP endpoint. Do not use the docs URL. Do not append another /mcp.

Transport mismatch

Citlyze uses Streamable HTTP. If a client asks for transport type, choose http first. If the client uses protocol names, choose streamable-http.

Do not choose sse unless Citlyze publishes a separate SSE endpoint.

Client only supports stdio

Some clients only launch local stdio MCP servers. Use mcp-remote as a local bridge to the Citlyze Streamable HTTP endpoint, or use a client with native remote HTTP support.