MCP Troubleshooting
Fix common MCP connection and data issues.
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. MCP and the REST API require the same plan capability.
No completed window
Many tools default to the latest completed measurement window. If the workspace is new, tracking has not finished a window yet; wait for the next scheduled run to complete, then check the dashboard for results.
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/mcpDo 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. Citlyze does not offer an SSE endpoint.
GET requests return 405
The MCP endpoint only accepts POST. Probing it with GET (for example with
curl or a client's connectivity check) returns a 405 response. That is
expected and does not mean the server is down; connect with a Streamable HTTP
MCP client instead.
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.