Cituna Mcp
Track how 6 AI engines cite your brand, daily, with live Google Search Console.
- Transport
- Not stated
- Package
- —
- Registry id
- com.cituna/cituna-mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
The AI visibility tool you use from inside the AI. Every other tool in this category hands you a dashboard and leaves the thinking to you. Cituna puts the measurements where you already do the reasoning: ask Claude why ChatGPT never mentions you, and it can pull the answer receipts, cross-check them against what Google already sends you, and queue the page that fixes it, without you opening a tab.
Links: npm package ·
MCP registry listing
(com.cituna/cituna-mcp) · docs and pricing
Two client integrations for Cituna, which tracks how AI answer engines — ChatGPT, Perplexity, Gemini, Claude, Grok and Google AI Overviews — mention and cite your brand.
Both are thin clients over the Cituna REST API. They hold no secrets: you paste a personal API key, and everything else (Google OAuth refresh tokens, the database, the scan pipeline) stays server-side.
| What it is | |
|---|---|
cituna-mcp (this package) |
An MCP server, so Claude can query your visibility data, gaps and Search Console directly |
looker-connector/ |
A Google Apps Script community connector for Looker Studio dashboards |
MCP server
Install
npx cituna-mcp
Or wire it into Claude Desktop / Claude Code:
{
"mcpServers": {
"cituna": {
"command": "npx",
"args": ["-y", "cituna-mcp"],
"env": { "CITUNA_API_KEY": "cituna_sk_..." }
}
}
}
Generate a key in the app under Integrations → Claude / MCP access. It is shown once. The same key works for the Looker connector.
Configuration
| Variable | Required | Default | Notes |
|---|---|---|---|
CITUNA_API_KEY |
yes | — | Personal API key, cituna_sk_… |
CITUNA_API_URL |
no | https://cituna.com |
Point at a local backend for development |
Tools
Twelve read tools work on Starter and above (one exception: list_keywords
reads the keyword dataset that is part of Pro). The four write tools —
run_scan, set_gap_status, queue_article and mark_article_published —
require Pro. The 3-day trial is app-only and has no MCP access.
| Tool | Does |
|---|---|
whoami |
Confirm the connection, plan and usage meters. Start here. For Search Console state use gsc_status. |
list_brands |
Brands/domains tracked in your workspace |
get_visibility |
The daily prompt × engine grid: cited or not, position, per-cell status |
get_engine_answers |
What an engine actually said for a prompt, and who it cited instead |
list_audits / get_audit |
Scan history and a single scan's scores |
list_gaps / set_gap_status |
The fix queue, and moving items through todo → doing → done |
list_keywords |
Keywords with real demand, each with the stage of the page behind it. Filter stage: "none" for demand nothing has been written for yet. Needs Pro (the keyword dataset is a Pro feature) |
list_content_queue |
What AutoSEO already has in flight, so you never queue a topic twice |
queue_article |
Queue a keyword so AutoSEO drafts it on the next run |
mark_article_published |
Tell Cituna a page is live, so it stops suggesting the topic and never writes a competing page |
gsc_status / gsc_overview / gsc_query |
Google Search Console, if connected |
run_scan |
Trigger a fresh scan |
Connecting Google Search Console
From the project's README.