Cituna MCP vs Proofsource
A side-by-side look at the Cituna MCP and Proofsource MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cituna MCP for marketing work as a local process; choose Proofsource for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cituna MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CITUNA_API_KEY, CITUNA_API_URL. - You want tools like
whoami, list_brands, get_visibility.
Choose Proofsource when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_brands, list_topics, get_visibility.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | CITUNA_API_KEYCITUNA_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 20 | 14 |
| Full listing | View Cituna MCP | View Proofsource |
Tools & capabilities
Cituna MCP tools 20
whoamiConfirm the connection, plan and usage meters. Start here. For Search Console state use `gsc_status`.list_brandsBrands/domains tracked in your workspaceget_visibilityThe daily prompt × engine grid: cited or not, position, per-cell statusget_engine_answersWhat an engine actually said for a prompt, and who it cited insteadset_promptsEdit the tracked buyer questions: add, remove, enable or disable them, or replace the whole setlist_auditsScan history and a single scan's scoreslist_gapsThe fix queue, and moving items through todo → doing → donelist_keywordsKeywords 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_queueWhat AutoSEO already has in flight, so you never queue a topic twicelist_articlesThe articles AutoSEO wrote, with live URLs and when each was published, sent, edited and refreshed; and one article's stored textqueue_articleQueue a keyword so AutoSEO drafts it on the next runmark_article_publishedTell Cituna a page is live, so it stops suggesting the topic and never writes a competing page- +8 more on the listing page
Proofsource tools 14
list_brandsThe brands this workspace tracks in AI answers, with ids and websites. Call first; every other tool takes a brand_id.list_topicsThe topics and buyer questions this workspace asks ChatGPT, Perplexity, Claude and Google AI for a brand. Gives the topic_id create_prompt needs.get_visibilityHow often ChatGPT, Perplexity, Claude and Google AI mention the brand when buyers ask about its category. by=engine (default): mention rate, share of voice, average position, citation share and sentiment per engine, with the change from the previous period. by=question: each buyer question's mention rate and rank.get_competitorsThe competitors AI answers name for the brand's buyer questions, per engine, with each one's share of voice against the brand and how it changed over the window.get_citationsThe websites AI answers cite for the brand's buyer questions, ranked by share of citations and by how many answers cite them, and where the brand's own site ranks.get_changesWhat moved over the window: the daily mention-rate trend, how much the engines' answers changed, notable changes on competitors' websites, and new pages about the category.list_fix_opportunitiesThe gaps that keep AI engines from citing or recommending the brand, each with its evidence and the suggested fix. Gives the gap_id mark_fix_shipped needs.get_fix_verificationEach fix marked shipped for the brand with its mention rate before and after and a verdict: moved (beyond normal answer churn), within_noise, or awaiting_samples. Fixes marked "Not a fix" are left out; auto-detected page changes carry source auto_detected.create_promptAdds a buyer question to a topic so it is asked on every engine in the plan from the next run. Counts toward the plan's question limit. Calling again with the same text returns the existing question, never a duplicate.mark_fix_shippedRecords that a fix shipped, against a gap_id from list_fix_opportunities or a published content_draft_id, so get_fix_verification can measure whether it moved the brand's mention rate. Calling again with the same fix and description returns the existing record.add_brandStart measuring a brand: does ChatGPT, Perplexity, Claude or Google AI mention it, and who does AI recommend instead? Give the brand's website (or its app store, Google Maps, YouTube or Instagram link). It reads the site, picks the buyer questions, and starts the first scan across the AI engines. Reading the site takes 1-2 minutes; if it is still running, call again with the same link and it picks up the same run, never a second one. Returns the brand_id; then use get_scan_status.get_scan_statusProgress of a brand's first scan after add_brand: the stage, how many AI answers are in out of how many expected, per engine, and when it should finish. Once complete, use get_visibility for the results.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cituna MCP
{
"mcpServers": {
"cituna-mcp": {
"command": "npx",
"args": [
"-y",
"cituna-mcp"
],
"env": {
"CITUNA_API_KEY": "YOUR_CITUNA_API_KEY_HERE",
"CITUNA_API_URL": "YOUR_CITUNA_API_URL_HERE"
}
}
}
}
Proofsource
{
"mcpServers": {
"proofsource": {
"command": "npx",
"args": [
"-y",
"proofsource"
]
}
}
}
Frequently asked questions
Cituna MCP is categorized under Marketing and uses a local stdio subprocess. Proofsource belongs to Marketing and uses a remote HTTP/SSE transport. Pick Cituna MCP for marketing work and Proofsource for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cituna MCP has no declared pricing — check the project's own site. Proofsource is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cituna-mcp and proofsource as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cituna MCP has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Proofsource has 68/100 (Great) with 2 views, 0 installs and 0 GitHub stars.