Llmpulse MCP vs Maxaeo AI Visibility MCP

In-depth architectural comparison of the Llmpulse MCP and Maxaeo AI Visibility MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Llmpulse MCP when:

• You need dedicated capabilities in the Marketing domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (Paid Service).
• You have access to required keys: LLMPULSE_API_KEY.
• Primary tools included: Brand mention, citation, and sentiment tracking across AI search engines, Competitor share-of-voice and top-source analytics, GEO (generative engine optimization) performance metrics.

Explore Llmpulse MCP Details

Choose Maxaeo AI Visibility MCP when:

• You need dedicated capabilities in the Marketing domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: check_llms_txt, audit_ai_crawler_readiness, build_ai_visibility_report.

Feature & Specification Comparison

Specification	Llmpulse MCP LLM-Pulse Marketing	Maxaeo AI Visibility MCP maxaeo Marketing
Summary	Hosted MCP server for LLM Pulse AI visibility analytics, including brand mentions, citations, sentiment, share of voice, recommendations, GEO Writer, Search Console, and AI traffic via a Streamable HTTP endpoint.	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.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "llm-pulse-llmpulse-mcp": {
      "url": "https://api.llmpulse.ai/api/v1/mcp"
    }
  }
}

{
  "mcpServers": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "maxaeo-ai-visibility-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons