Cituna MCP

What cituna-mcp MCP server does

The cituna-mcp MCP server exposes Cituna's AI visibility data through the Model Context Protocol. Cituna tracks whether configured brands and domains are mentioned or cited by ChatGPT, Perplexity, Gemini, Claude, Grok, Google AI Overviews, and Google AI Mode. The server lets an MCP client inspect that data without opening the Cituna dashboard.

Use whoami to confirm the account, plan, and usage meters, then list_brands to see the tracked domains. get_visibility returns the daily prompt-by-engine results, including citation state, position, and cell status. get_engine_answers provides the answer text and competing sources cited for a prompt. Audit history, individual scores, gaps, keywords, and AutoSEO's content queue are also available.

How it works

The package is a thin client over Cituna's REST API. It does not store Google OAuth refresh tokens or other backend data locally. Authentication uses a personal Cituna API key supplied to the MCP process. The standard launch command is npx cituna-mcp, making it suitable for MCP clients that can start a stdio server.

Cituna's built-in MCP prompts provide reusable workflows for uncited prompts, Google-to-AI gaps, competitor comparisons, weekly reviews, and fix prioritization. These workflows read existing data and do not themselves start a paid scan. run_scan can request a fresh scan when the account has access to that operation.

Setup and configuration

Install or launch the package with:

npx cituna-mcp

Configure the client with CITUNA_API_KEY, using a key generated in Cituna under Integrations → Claude / MCP access. CITUNA_API_URL is optional and defaults to https://cituna.com; it can point to a local backend during development. Node.js 20 or newer is required.

Google Search Console is not authorized inside the cituna-mcp MCP server. Connect it once in the Cituna app, grant read-only access, and choose an account containing a verified property. Use gsc_status to confirm the connected account and available properties. Disconnecting in the app revokes access.

Tools and capabilities

Available operations include:

• Inspect account access, brands, visibility grids, engine responses, audits, gaps, keywords, and content queues.
• Read Search Console connection state, overviews, and queries when the service is connected.
• Move gaps between todo, doing, and done with set_gap_status.
• Queue an article for AutoSEO with queue_article and mark a live page with mark_article_published.
• Trigger a new scan with run_scan.

Read tools are available on Starter and higher plans, except that the keyword dataset requires Pro. The write operations run_scan, set_gap_status, queue_article, and mark_article_published require Pro access.

Limitations and notes

The 3-day trial is app-only and does not include MCP access. Google Search Console data depends on a prior connection in the Cituna app and a verified property; an incorrect property selection can produce empty results. API keys do not expire automatically, so an invalid-key error usually indicates revocation, a typo, lost account access, or an incorrectly configured API URL. Do not add a trailing path or redirect to CITUNA_API_URL, because a cross-origin redirect can remove the authorization header.

The cituna-mcp MCP server does not itself provide Google OAuth consent or local storage for the Search Console refresh token. It also cannot make the Looker Studio connector available through MCP; that is a separate integration in the repository.