Cituna MCP server

Bring Cituna into Claude (Desktop, Code, or any MCP client). This server is a thin bridge over the Cituna backend: it authenticates as you and calls the same endpoints the app uses, so Google's OAuth refresh token and your database stay server-side and nothing sensitive lives in the MCP.

It exposes three things Claude can work with directly:

• Daily visibility tracking — the core deliverable. Your tracked prompts are re-asked every day across all six engines (ChatGPT, Perplexity, Gemini, Claude, Grok, Google AI Overviews); get_visibility returns the latest prompt×engine grid (cited? which position? which mode?) plus your current score, and get_engine_answers returns the receipts — what each engine actually said, the brands it cited, and the source URLs.

• AI-visibility audits — per-engine citation scores across all six engines, the query×engine citation matrix, competitors cited, and a prioritised gap/action queue you can update from the chat.

• Live Google Search Console — clicks / impressions / CTR / position, top queries and pages, and arbitrary Search Analytics queries.

Claude  ⇄  (stdio, MCP)  ⇄  this server  ⇄  (HTTPS + your key)  ⇄  Cituna backend  ⇄  AI engines + Google Search Console

Tools

Read tools work from Starter; write tools — the two tagged ✍︎ Pro — require Pro or higher (see Plans). The 7-day free trial is app-only and has no MCP access.

Related MCP server: Google Search Console MCP Server

Plans

The MCP server is included from the Starter plan ($39/mo) and up (Starter / Pro / Max, which map to internal solo / agency / scale). There is no free MCP — the 7-day trial is app-only, and an ended trial with no plan can't call it.

Read / write split. On Starter the MCP is read-only: read your audits, gaps, brands, and Search Console data all you like. The write tools — run_scan (spends a scan) and set_gap_status (mutates your action queue) — require Pro or higher; on Starter you still run scans and work the queue in the app, just not from Claude. Every MCP call also counts against your plan's monthly MCP-call allowance (Starter 5k / Pro 10k / Max 30k). If a write tool returns "…is a write action — it needs the Pro/Max plan", upgrade at https://cituna.com/pricing.

Install

No clone, no build — npx fetches it:

npx -y cituna-mcp   # (normally launched by your MCP client, see below)

From source (for development):

git clone https://github.com/Cituna/cituna-mcp && cd cituna-mcp
npm install && npm run build   # → node dist/index.js

Configure

Set CITUNA_API_URL (backend base URL, default https://cituna.com) plus one auth option, checked in this priority order:

1. Personal API key — recommended. In the app: Integrations → "Claude / MCP access" → Generate token, copy the cituna_sk_… value. Long-lived, revocable in the app, and not your password. → CITUNA_API_KEY

2. A session JWT. Log into the app, DevTools → Application → Cookies, copy cituna_token. Works but expires ~30 days. → CITUNA_TOKEN

3. Email + password. The server logs in and auto-refreshes on expiry. → CITUNA_EMAIL + CITUNA_PASSWORD

Claude Code

claude mcp add cituna --scope user \
  --env CITUNA_API_KEY=cituna_sk_your_generated_key \
  -- npx -y cituna-mcp

(The backend URL defaults to https://cituna.com; add --env CITUNA_API_URL=… only to point at a different backend.)

Then in a Claude Code session: /mcp to confirm it's connected, and ask "what changed in my AI visibility this week?"

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "cituna": {
      "command": "npx",
      "args": ["-y", "cituna-mcp"],
      "env": {
        "CITUNA_API_KEY": "cituna_sk_your_generated_key"
      }
    }
  }
}

Restart Claude Desktop. The tools appear under the 🔌 menu.

Running from source instead of npm? Use "command": "node", "args": ["/absolute/path/to/mcp/dist/index.js"].

Built-in prompts (v1.5+)

The server ships five reusable analysis workflows via the MCP prompts API. In Claude they show up in the prompt/command picker; each one runs a worked recipe over the tools, including the joins between Search Console and the engine answers that a generic SEO tool cannot make.

All five are read-only by default; none of them triggers a paid scan on its own.

Example prompts

• "How is acme.com doing in AI search today — which prompts and engines cite us?" (get_visibility)

• "For acme.com, on the prompt best CRM for dentists, what did each engine actually say and who did they cite?" (get_engine_answers)

• "What changed in my AI visibility this week?" (uses list_audits → get_audit)

• "Which gaps are open for acme.com? Mark the schema one done." (list_gaps → set_gap_status)

• "Run a fresh visibility scan for acme.com and summarise the top 3 gaps." (run_scan)

• "Which AI engines cite us, and for which questions?" (the citation matrix from get_audit)

• "How did example.com do in Search over the last 28 days?" (gsc_overview)

• "Break down example.com traffic by country, then by device." (gsc_query)

• "Show queries containing 'pricing' for example.com — filter query contains pricing." (gsc_query)

Connecting Google Search Console

The gsc_* tools need a one-time connect in the Cituna app, not here. There is no Google OAuth in this server, by design: the browser consent flow happens in the app, and the resulting refresh token is stored server-side only.

1. In the app, open Integrations and click Connect Google Search Console (paid plans; the trial does not include GSC).

2. Google will ask to grant Cituna read-only Search Console access (webmasters.readonly). Cituna never gets write access to anything Google.

3. Pick the Google account where your domain is a verified Search Console property. This is the step people miss: if the account you choose has never verified the domain, everything connects fine and every query still comes back empty, because Google has nothing to show that account.

4. Back here, run gsc_status. It lists the connected account and every property it can query. If your domain is not in that list, fix it in Search Console (verify the property), not in Cituna.

Disconnecting in the app (Integrations, Disconnect) revokes access for this server instantly as well.

How auth reaches Google

This server never holds Google credentials. It sends your Cituna key/JWT as a Bearer token to the backend; the backend looks up your workspace's stored GSC refresh token, mints a short-lived Google access token, and queries the Search Console API. Disconnecting GSC in the app instantly cuts off this server too.

Troubleshooting

Requires Node 18.17+.

About this repository

The public Cituna/cituna-mcp repo is a published mirror, not the working tree: the server is developed in Cituna's private monorepo and released on tag, so the tool surface and engine list stay pinned to what the API actually serves. Pull requests against the mirror can't be merged directly, but issues are read and acted on, so please do open them.

Looking for BI dashboards instead of a chat client? Cituna also ships a Looker Studio connector. See cituna.com/integrations.

MIT licensed. Bugs and requests: https://github.com/Cituna/cituna-mcp/issues