One workspace endpoint
A single MCP endpoint covers your workspace. Each project-level tool accepts a project_id argument to scope the call.
Features · MCP Server
Connect MCP-compatible AI tools to Ceyo visibility data, prompts, actions, competitors, and analytics.
Same API key
JSON-RPC 2.0
What MCP unlocks
Ceyo MCP lets AI tools read and work with the same project state your team uses in the platform, scoped by workspace API key and project ID.
A single MCP endpoint covers your workspace. Each project-level tool accepts a project_id argument to scope the call.
The MCP server uses the same Ceyo API key as the REST API, with X-Api-Key or Authorization bearer headers.
Expose visibility metrics, prompts, LLM responses, citations, competitors, actions, fan-out queries, and analytics.
Connect Cursor, Claude Desktop, n8n, or a generic MCP client so agents can inspect Ceyo data directly.
The MCP docs include setup paths for Cursor, Claude Desktop, n8n, and generic MCP clients, with OAuth-based remote clients marked as coming soon.
The MCP server is not just a metrics endpoint. It gives agents structured access to workspace, project, prompt, action, competitor, suggestion, fan-out, and analytics data.
The server implements Model Context Protocol over HTTP using JSON-RPC 2.0. Authentication happens before tool calls, and each project operation is scoped by project_id.
Setup flow
Create or reuse a workspace API key from Workspace settings, the same credentials used by the REST API.
Configure your MCP client with the Ceyo MCP endpoint and pass the API key through an accepted header.
Ask the agent to list projects to confirm the workspace connection and available project IDs.
Use project_id scoped tool calls to inspect visibility, prompts, actions, competitors, fan-out queries, and analytics.
See how the MCP server lets your agents inspect visibility, prompts, competitors, actions, and analytics without switching back to the dashboard.