GEO MCP vs Citable MCP
A side-by-side look at the GEO MCP and Citable MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GEO MCP for marketing work over a hosted endpoint; choose Citable 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?
Choose GEO MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Citable MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CITABLE_WALLET, CITABLE_MAX_PRICE, CITABLE_API. - You want tools like
citable_prices, citable_connect, citable_keyword_suggest.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 48/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | CITABLE_WALLETCITABLE_MAX_PRICECITABLE_API |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,361 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 19 |
| Full listing | View GEO MCP | View Citable MCP |
Tools & capabilities
GEO MCP tools
No tool names declared yet. Check the project README from the listing page.
Citable MCP tools 19
citable_pricesFree. Lists Citable's SEO endpoints with current per-call USDC prices, plus the wallet that pays: address (the one to fund), walletMode (keypair or sign-in), balanceUsdc and funded. When it is empty, `setup` gives the two ways to fund it — put them to the user. Call this first.citable_connectFree. For people who do not use crypto. Returns a link to open in a browser: sign in at Citable with Google or email, add a few dollars of USDC, click Connect — the agent then pays from that wallet. The link works for 15 minutes; when the user says it is done, call citable_prices to confirm (walletMode becomes sign-in). {status:true} only reports; {reset:true} disconnects and returns to the keypair. The first connect installs Para's SDK under ~/.config/citable/para (about 200 MB, once).citable_keyword_suggestPaid ($0.005 USDC per call). Expands a seed keyword into autocomplete suggestions, related queries and questions, deduped and ranked across Google, YouTube and Bing. Returns `suggestions[]` and `questions[]` with a 0–1 prominence score, the sources each came from, and whether the keyword still contains the seed.citable_onpage_auditPaid ($0.01 USDC per call). Fetches one URL and returns a scored on-page audit: title, meta description, canonical, robots, viewport, lang, heading counts and text, word count, internal/external links, image alt coverage, Open Graph, JSON-LD types, HTTP details, and 15 weighted checks with a 0–100 score. Not charged if the page cannot be fetched.citable_ai_visibilityPaid ($0.05 USDC per engine asked; $0.20 for all four). Asks the AI answer engines (Perplexity, Gemini, OpenAI, Claude — whichever the deployment has configured) a prompt through their official APIs and reports which ones cite the domain: `mentioned`, 1-based `position` in each engine's citation list, and the full cited-domain list per engine. One run per engine — answers vary between runs, so call 2–3 times for signal. Not charged if no engine answers.citable_rank_checkPaid ($0.012 USDC per call). Google organic position of a domain for a keyword via a licensed SERP feed: 1-based `position` (null if outside the checked window), the ranking URL and title, plus the top-10 result list. Not charged if the feed is unavailable.citable_keyword_researchPaid ($0.06 USDC per call). One seed returns keywords AND questions, merged from public autocomplete and the paid keyword index, with search volume, CPC, difficulty and intent attached. Each row says which sources found it — both is the strongest signal. Cheaper than citable_keyword_ideas plus citable_keyword_metrics separately; reach for those only when you want to control exactly what you pay for. Not charged on failure.citable_keyword_ideasPaid ($0.05 USDC per call). Keyword research: one seed returns up to 100 keywords that contain it, each with search volume, CPC, competition, difficulty and intent, ordered by volume. Full-text matched, so results stay on topic. Use citable_keyword_suggest for the exact phrasings people type (no volume), and citable_keyword_metrics when you already have a shortlist. Not charged on failure.citable_keyword_metricsPaid ($0.03 USDC per call, covers the whole batch). Search volume, CPC, competition, keyword difficulty and search intent for 1–20 keywords — licensed clickstream-derived estimates. Answers in request order; unknown keywords return null metrics. Pair with citable_keyword_suggest: expand a seed there, price the shortlist here. Not charged if the metrics feed is unavailable.citable_top_cited_pagesPaid ($0.22 USDC per call). Which pages of a domain AI engines cite most, from an aggregated index of AI answers — per-page mentions, AI search volume, per-engine and per-language splits, plus domain totals. Answers 'what already works on this site — write more of that'. Not charged if the index is unavailable.citable_citability_reportPaid ($0.30 USDC per call; $0.43 bought separately). One call bundles the on-page citability audit, AI visibility across all configured engines, and the domain's top AI-cited pages. Answers: can AI read this site, who cites it today, and which pages already work. Not charged on failure.citable_cited_promptsPaid ($0.25 USDC per call). The real questions AI answer engines cite a domain for, from an aggregated index of AI answers — question, answer snippet, AI search volume, and the exact URL cited. These are observed prompts, never generated ones, so use this to discover what to track instead of inventing them. Repeated observations of one question are collapsed, with `observations` counting them. Point it at a competitor's domain to get the prompts they win and you do not. Not charged on failure.- +7 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.
GEO MCP
{
"mcpServers": {
"google-ads-meta-ads-seo-geo-mcp": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}
Citable MCP
{
"mcpServers": {
"zaialamm-citable-mcp": {
"command": "npx",
"args": [
"-y",
"citable-mcp"
],
"env": {
"CITABLE_WALLET": "YOUR_CITABLE_WALLET_HERE",
"CITABLE_MAX_PRICE": "YOUR_CITABLE_MAX_PRICE_HERE",
"CITABLE_API": "YOUR_CITABLE_API_HERE"
}
}
}
}
Frequently asked questions
GEO MCP is categorized under Marketing and uses a remote HTTP/SSE transport. Citable MCP belongs to Marketing and uses a local stdio subprocess. Pick GEO MCP for marketing work and Citable 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.
GEO MCP has no declared pricing — check the project's own site. Citable 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 google-ads-meta-ads-seo-geo-mcp and zaialamm-citable-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GEO MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 5,361 GitHub stars. Citable MCP has 60/100 (Good) with 2 views, 0 installs and 0 GitHub stars.