Cituna MCP vs Vibeads MCP

A side-by-side look at the Cituna MCP and Vibeads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Cituna MCP logoCituna MCPMarketing · Local subprocess (stdio)Track how 6 AI engines cite your brand, daily, with live Google Search Console.55GoodAuth: not declaredVibeads MCP logoVibeads MCPMarketing · Local subprocess (stdio)Manage Google Ads from Claude: read metrics, draft campaigns, publish with human approval.57GoodAuth: not declared

Verdict: choose Cituna MCP for marketing work as a local process; choose Vibeads MCP for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Cituna MCP logoChoose 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.
Explore Cituna MCP

Vibeads MCP logoChoose Vibeads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: VIBEADS_API_KEY.
  • You want tools like list_campaigns, get_campaign_details, get_account_health_score.
Explore Vibeads MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCituna MCP logoCituna MCPVibeads MCP logoVibeads MCP
CategoryMarketingMarketing
Quality signal55/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsCITUNA_API_KEYCITUNA_API_URLVIBEADS_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars11
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools2029

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 workspace
  • get_visibilityThe daily prompt × engine grid: cited or not, position, per-cell status
  • get_engine_answersWhat an engine actually said for a prompt, and who it cited instead
  • set_promptsEdit the tracked buyer questions: add, remove, enable or disable them, or replace the whole set
  • list_auditsScan history and a single scan's scores
  • list_gapsThe fix queue, and moving items through todo → doing → done
  • list_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 twice
  • list_articlesThe articles AutoSEO wrote, with live URLs and when each was published, sent, edited and refreshed; and one article's stored text
  • queue_articleQueue a keyword so AutoSEO drafts it on the next run
  • mark_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

Vibeads MCP tools 29

  • list_campaignsYour campaigns in VibeAds (published, imported and drafts) with status, budget and category. Campaigns only in your Google Ads account are listed by `find_campaigns_to_import
  • get_campaign_detailsDeep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnostics
  • get_account_health_score0-100 score + letter grade across 6 dimensions, optionally per-campaign
  • get_search_term_analysisWasted spend + winners from each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)
  • get_diagnosticsLatest agent-optimize diagnostics with severity + recommended fix (up to 50)
  • find_campaigns_to_importBefore importing: the campaigns in your Google Ads account, read from Google Ads, each marked with whether it is in VibeAds (VibeAds manages only the campaigns in it). Called `list_google_ads_campaigns` in 0.2.15
  • get_performance_reportOne campaign's or a whole account's figures for a period you choose (a preset or two dates, up to 90 days), read live from Google Ads, optionally by day, device, hour, ad group, keyword or location. Money in the account's currency. VibeAds builds every query; the assistant only picks the period and…
  • audit_google_ads_accountAn audit of one connected Google Ads account, read live from Google Ads: up to 25 Search campaigns over the last 30 days, whether or not they are in VibeAds, with a 0-100 health score and grade for the account and each campaign, the issues grouped by check with what fixes each in Google Ads, and ea…
  • list_keywordsOne published campaign's ad groups, keywords and negative keywords, read live from Google Ads: match type, status, max CPC and 30 days of clicks, cost and conversions
  • research_keywordsKeyword ideas from Google's Keyword Planner for seed keywords, a web page or both, in the places you name: average monthly searches, competition and top-of-page bid range. Pro/Max, 2 credits (a repeat within 90 days is free)
  • list_google_ads_accountsEvery connected Google Ads account, switched on or not, with the manager account (MCC) each client account sits under
  • list_google_recommendationsGoogle's own recommendations for an account (its Recommendations page), with Google's estimate and whether each can be applied from the chat
  • +17 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 (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Vibeads MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-335": {
      "command": "npx",
      "args": [
        "-y",
        "@vibeads/mcp"
      ],
      "env": {
        "VIBEADS_API_KEY": "YOUR_VIBEADS_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Cituna MCP is categorized under Marketing and uses a local stdio subprocess. Vibeads MCP belongs to Marketing and uses a local stdio subprocess. Pick Cituna MCP for marketing work and Vibeads MCP 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. Vibeads MCP has no declared pricing — check the project's own site. 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 mcp-335 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. Vibeads MCP has 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars.