Seo Ai Visibility vs GEO MCP
A side-by-side look at the Seo Ai Visibility and GEO MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Seo Ai Visibility for marketing work as a local process; choose GEO MCP 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 Seo Ai Visibility when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
seo_llm_answer.
Choose GEO MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 52/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,879 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Seo Ai Visibility | View GEO MCP |
Tools & capabilities
Seo Ai Visibility tools 1
seo_llm_answerDoes `<brand>` appear in ChatGPT's answer for `<question>` — runs a prompt through an LLM and returns its answer plus any cited sources/links, for AI-visibility (GEO) analysis: see what an LLM says about a brand, topic, or query and which sources it cites. Example: seo_llm_answer({ user_prompt: "Wh…
GEO MCP tools
No tool names declared yet. Check the project README from 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.
Seo Ai Visibility
{
"mcpServers": {
"seo-ai-visibility": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-seo-ai-visibility"
]
}
}
}
GEO MCP
{
"mcpServers": {
"google-ads-meta-ads-seo-geo-mcp": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}
Frequently asked questions
Seo Ai Visibility is categorized under Marketing and uses a local stdio subprocess. GEO MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick Seo Ai Visibility for marketing work and GEO 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.
Seo Ai Visibility has no declared pricing — check the project's own site. GEO MCP has no declared pricing — check the project's own site. 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 seo-ai-visibility and google-ads-meta-ads-seo-geo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Seo Ai Visibility has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. GEO MCP has 49/100 (Fair) with 1 views, 0 installs and 5,879 GitHub stars.