Ext Ops Panel
Open dashboard
Comparison

seo-intelligence vs SEO GEO Intelligence

seo-intelligence is a plugin bundle for AI coding tools published by trentiums. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SEO GEO Intelligence is an MCP server published by atul0016. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceseo-intelligenceSEO GEO Intelligence
Claude Code: claude-plugins-community Listed
Version: 3.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 80
Downloads/week (PyPI): 19
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

seo-intelligence vs SEO GEO Intelligence
Factseo-intelligenceSEO GEO Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (seo-geo-intelligence-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 43, secrets among them: 1
Parts of the bundle (differs)23Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/trentiums/seo-intelligenceNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

seo-intelligence

In its own words, on Claude Code: claude-plugins-community:

AI-powered SEO analysis, competitor comparison, and ranking plans. Analyze any page's SEO health, compare against top-ranking competitors, and get prioritized action plans to rank higher.

SEO GEO Intelligence

In its own words, on Official MCP Registry:

SEO and AI-answer visibility intelligence for search, content gaps, and GEO actions.

How to run each

seo-intelligence As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install seo-intelligence@claude-community

SEO GEO Intelligence As a local MCP server: PyPI package

Claude Code
claude mcp add --env "EARNALL_MCP_LICENSE_KEY=<YOUR_EARNALL_MCP_LICENSE_KEY>" --transport stdio seo-geo-intelligence -- uvx seo-geo-intelligence-mcp

Requires: EARNALL_MCP_LICENSE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only seo-intelligence asks for

  • GOOGLE_CLOUD_API_KEY (secret)
  • OPENAI_API_KEY (secret)
  • PERPLEXITY_API_KEY (secret)
  • SERPAPI_KEY (secret)

Only SEO GEO Intelligence asks for

  • EARNALL_MCP_ACTIVATION_ID
  • EARNALL_MCP_LICENSE_API
  • EARNALL_MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: seo-intelligence · What it can do: SEO GEO Intelligence · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built