Citely[1]

Workflows · MCP

Connect your visibility data to any agent.

Citely's MCP server connects your visibility data to agents, automations, reports, and internal tools — so the data doesn't stay locked inside one dashboard.

MCP · Connected clients

Illustrative — kayahouse.sg workspace (demo)

  • Active connections3
  • Queries this week212
  • Scoped tokens issued5

A standard MCP server

Connect Cursor, Claude Code, Windsurf, ChatGPT, n8n, and internal tools to your visibility data via one MCP endpoint — no bespoke integration per client.

Read access to your full dataset

Query mentions, citations, sentiment, and audit results directly, instead of exporting CSVs into another system.

Trigger workflows from outside Citely

Kick off a content brief or a technical audit from your own internal tooling, using the same actions available in the dashboard.

Built for internal automation

Wire visibility data into a WhatsApp or Slack digest, internal dashboards, or a nightly report — wherever your team already looks.

Scoped, revocable access

Issue scoped tokens per integration and revoke them individually, without disrupting other connected tools.

One protocol, many clients

As more AI tools adopt MCP, the same connection keeps working — no per-client integration work required.

Setup

Citely’s MCP server is part of the paid product. The config below shows what wiring looks like once your workspace is active.

Connect in one line

Cursor — .cursor/mcp.json

{
  "mcpServers": {
    "citely": {
      "url": "https://mcp.citely.sg/mcp"
    }
  }
}

Claude Code — terminal

claude mcp add citely --transport http https://mcp.citely.sg/mcp

See where you stand — free.

Run a free check on your own domain in seconds, or talk to us about what a full rollout would look like.