Seo Tools MCP vs Llmpulse MCP

In-depth architectural comparison of the Seo Tools MCP and Llmpulse 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 Seo Tools MCP when:

• You need dedicated capabilities in the Marketing domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (BYOK (Pay Provider Direct)).
• Primary tools included: Eight read-only stdio MCP servers, SERP, image, news, video, maps, and index-checking tools, Yandex Wordstat frequency, dynamics, and regional analysis.

Explore Seo Tools MCP Details

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.

Feature & Specification Comparison

Specification	Seo Tools MCP antohins Marketing	Llmpulse MCP LLM-Pulse Marketing
Summary	Five read-only SEO servers for the Google/Yandex (RU/CIS) market: SERP (XMLStock), Yandex Wordstat, Google Search Console (Search Analytics + URL Inspection), Yandex.Webmaster, and Yandex.Metrica. 38 tools, multi-account, OAuth with auto-refresh. Install: npx -y seo-tools-mcp-.	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.
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": {
    "antohins-seo-tools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-xmlstock"
      ]
    }
  }
}

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

Related MCP Server Comparisons