Ext Ops Panel
Open dashboard
Comparison

digestseo-geo vs Bing Webmaster AI CLI MCP

digestseo-geo is a plugin bundle for AI coding tools published by akzar1el. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Bing Webmaster AI CLI MCP is an MCP server published by stufently. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplacedigestseo-geoBing Webmaster AI CLI MCP
Community marketplace akzar1el/mcp-geo Listed
Version: 0.3.29
Forks (GitHub): 2
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
Downloads/month (PyPI): 0
Downloads/week (PyPI): 169
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.1.4
Downloads/month (PyPI): 0
Downloads/week (PyPI): 169
Forks (GitHub): 0
Stars (GitHub): 1
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

digestseo-geo vs Bing Webmaster AI CLI MCP
Factdigestseo-geoBing Webmaster AI CLI MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)38 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)2026-10-26 (better)2026-10-15 (worse)
Where it runs (differs)On your machine (@digestseo/mcp-geo)On your machine (bing-webmaster-ai-cli-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/akzar1el/mcp-geogithub.com/stufently/bing-webmaster-ai-cli-mcp
Changes in the last 7 days (differs)50
First seen (differs)2026-10-132026-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

digestseo-geo

In its own words, on Community GitHub marketplaces:

Track brand citations and AI visibility across ChatGPT, Claude, Perplexity, Gemini, Grok, Google AI Overviews, and Google AI Mode.

Bing Webmaster AI CLI MCP

In its own words, on Official MCP Registry:

Read Bing Webmaster data and change it, directly or through a reviewed plan.

How to run each

digestseo-geo As a Claude Code plugin

Claude Code
/plugin marketplace add akzar1el/mcp-geo
/plugin install digestseo-geo@digestseo-mcp

Bing Webmaster AI CLI MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "BING_WM_API_KEY=<YOUR_BING_WM_API_KEY>" --transport stdio bing-webmaster-ai-cli-mcp -- uvx bing-webmaster-ai-cli-mcp

Requires: BING_WM_API_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

The marketplaces of digestseo-geo publish no settings it asks for, so we do not compare settings.

What it can do: digestseo-geo · What it can do: Bing Webmaster AI CLI MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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