What is the main functional difference between Seovendor and Maxaeo AI Visibility MCP?

Seovendor is categorized under Marketing and uses a remote HTTP/SSE transport. Maxaeo AI Visibility MCP belongs to Marketing and uses a local stdio subprocess. Pick Seovendor for marketing work and Maxaeo AI Visibility MCP for marketing.

How do I install Seovendor or Maxaeo AI Visibility MCP in Claude Desktop, Cursor, or Windsurf?

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.

Are Seovendor and Maxaeo AI Visibility MCP free to use, or do they require API keys?

Seovendor has no declared pricing — check the project's own site. Maxaeo AI Visibility MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Seovendor and Maxaeo AI Visibility MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add seovendor and maxaeo-maxaeo-ai-visibility-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Seovendor has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Maxaeo AI Visibility MCP has 61/100 (Good) with 4 views, 0 installs and 1 GitHub stars.

Seovendor vs Maxaeo AI Visibility MCP

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

SeovendorMarketing · Remote HTTP/SSEA FastMCP server that exposes SV's SEO and GEO tools natively to AI agents — Claude Desktop, Claude Code, Cursor, and any MCP-capable host. Built directly on the sv-cli core library: no duplicated resolver, auth, or async-task logic.44FairAuth: not declared

Maxaeo AI Visibility MCPMarketing · Local subprocess (stdio)Local-first AI visibility, GEO/AEO, and llms.txt audit MCP server for Claude, Codex, Cursor, and other agents. Checks AI crawler access, robots, sitemap, canonical, metadata, noindex, and JSON-LD; returns local-only and technical foundation scores, top issues, and action plans. Install: npx -y maxaeo-ai-visibility-mcp.61GoodAuth: no auth required

Verdict: choose Seovendor for marketing work over a hosted endpoint; choose Maxaeo AI Visibility MCP for marketing as a local process. You can also run both side by side in one mcpServers block.

Spec	S Seovendor	Maxaeo AI Visibility MCP
Category	Marketing	Marketing
Quality signal	44/100 · Fair	61/100 · Good
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	—	1
Directory activity	2 views 0 installs 0 upvotes	4 views 0 installs 0 upvotes
Tools	Not listed	3
Full listing	View Seovendor	View Maxaeo AI Visibility MCP

Seovendor vs Maxaeo AI Visibility MCP

Which MCP server should you choose?

S
Choose Seovendor when

Choose Maxaeo AI Visibility MCP when

Feature & specification comparison

Tools & capabilities

Seovendor tools

Maxaeo AI Visibility MCP tools 3

Ready-to-paste client configs

Seovendor

Maxaeo AI Visibility MCP

Frequently asked questions

SChoose Seovendor when