Open source · MIT · Python 3.12+
MCP server and CLI for Bing Webmaster Tools
Give an AI agent Bing Webmaster data: traffic, indexing, crawl issues, links, keywords, plus reviewed writes and IndexNow. Run with uvx, MIT.
What it does
- Read what Bing knows about your sites: traffic, indexing, crawl issues, inbound links and keywords.
- Reviewed writes by default: the agent records a plan, and only you apply it with bing-wm plan apply.
- Optional direct writes with BING_WM_ALLOW_WRITES=true, behind the same denylist, quota check and audit trail.
- Protocol-correct IndexNow submission that checks the key file before sending the batch.
- Verification codes and the API key are redacted in every response; untrusted text is marked as data.
- 59 of the 62 Microsoft API methods supported, over the JSON API only; SOAP and POX are absent.
Install
BING_WM_ALLOW_WRITES=false uvx bing-webmaster-ai-cli-mcp
That one command starts the stdio MCP server. Every client block below runs the same
uvx command. Create an API key in Bing Webmaster Tools under Settings → API Access
and pass it as BING_WM_API_KEY. Writes are planned for review unless you also set
BING_WM_ALLOW_WRITES=true — see Choosing a write path.
The package is on PyPI as
bing-webmaster-ai-cli-mcp. uvx caches what it installed and may keep running that
version; uvx bing-webmaster-ai-cli-mcp@latest checks PyPI again, and
uvx bing-webmaster-ai-cli-mcp==0.1.4 pins one. This README follows main, so a change
listed under Unreleased in the changelog is not in the PyPI release
yet. Since 0.1.3, BING_WM_ALLOW_WRITES=false is the default and the command above and
the client blocks below would behave the same without it. They still spell it out:
0.1.2 and earlier default to true, so a uvx cache still holding one of them would go
back to direct writes if the setting were left out.
To run main itself, use
uvx --from "git+https://github.com/stufently/bing-webmaster-ai-cli-mcp.git" bing-webmaster-ai-cli-mcp.
pip (Python 3.12+) installs the same package and puts bing-wm,
bing-webmaster-ai-cli-mcp and bing-webmaster-ai-cli-mcp-http on PATH — in a
virtualenv, or with pipx install bing-webmaster-ai-cli-mcp:
python -m pip install bing-webmaster-ai-cli-mcp
export BING_WM_API_KEY='…'
bing-wm sites list
The supported matrix is Python 3.12, 3.13, and 3.14. Development and images use the
exact versions in constraints.txt; published dependencies remain compatible floors.
Never put a real key in the repository. See configuration for
all settings.
Example prompts
- Why did my site lose clicks last week?
- Which pages is Bing failing to crawl, and why?
- Is this URL indexed, and when did Bing last fetch it?
- Submit this new page to Bing, but let me review the change first.
Choosing a write path
Read tools always execute immediately. For everything that changes Bing state, one setting picks between two paths:
export BING_WM_ALLOW_WRITES=false # default: writes are planned and applied by a human
export BING_WM_ALLOW_WRITES=true # opt in: writes go straight through
Read-only toward Bing is the default. Without BING_WM_ALLOW_WRITES=true the server
lists no tool that changes Bing, and the CLI refuses one-step writes. Here is the reason.
An agent using this server also reads pages, anchor text, crawl issues and search queries
written by strangers. A confirmation an agent can send is a confirmation prompt injection
can send, so as long as the agent can write, a poisoned string in someone else's anchor
text can reach your Bing account. With the default, nothing an agent does changes Bing
until you have read the plan and run bing-wm plan apply yourself. Opt in only for an
agent you trust with your Bing account.
Direct writes (BING_WM_ALLOW_WRITES=true)
The MCP server advertises one-step bing_<operation> tools, and the CLI accepts:
$ bing-wm submit-url example.com https://example.com/new-page --json
{"applied": true, "plan_id": "…", "operation": "submit_url", "result": null}
A direct write is not idempotent: retrying one records a new plan and sends the change
again. If a response is lost, read audit.jsonl or bing-wm plan list before repeating
the call.
Reviewed writes (default, BING_WM_ALLOW_WRITES=false)
The server advertises bing_plan_<operation> instead. Those tools send nothing:
$ bing-wm plan submit-url example.com https://example.com/new-page --json
{
"plan_id": "…",
"summary": "submit url https://example.com/new-page for https://example.com",
"apply_with": "bing-wm plan apply …"
}
$ bing-wm plan apply PLAN_ID
Apply this plan? [y/N]: y
No MCP tool takes a plan ID, in either mode: a plan recorded for review is applied or rejected only at the CLI, by you. A direct write applies the plan it creates in the same call and never touches one somebody else recorded. The plan path stays available while direct writes are on, so an agent can still propose a change for review.
What both paths share
A direct write is the same code with the human step removed: it records the same durable
plan and goes through the same apply boundary. A readable plan record, an append-only
audit trail, one-shot application, expiry, Bing's own submission quota, a site denylist
(BING_WM_DENIED_SITES) and restart-persistent local limits
(BING_WM_MAX_WRITES_PER_DAY) apply to both.
If the applying process is killed and leaves a lock behind, the command
bing-wm plan unlock PLAN_ID verifies that the recorded PID is gone before recovering
it. An unfinished plan becomes unknown_outcome and cannot be applied again; the
recovery is audited.
FAQ
How do I install the Bing Webmaster MCP server?
Run BING_WM_ALLOW_WRITES=false uvx bing-webmaster-ai-cli-mcp to start the stdio MCP server, with an API key from Bing Webmaster Tools (Settings, API Access) in BING_WM_API_KEY. pip install bing-webmaster-ai-cli-mcp (Python 3.12+) also puts the bing-wm CLI on PATH.
Can the agent change my Bing account?
Not by default. Without BING_WM_ALLOW_WRITES=true the server lists no tool that changes Bing: write tools only record a plan, and a human applies it at the CLI with bing-wm plan apply. No MCP tool takes a plan ID in either mode.
Which AI clients does it work with?
Any MCP client over stdio. The README has configs for Claude Code, Claude Desktop, Cursor, Windsurf and Zed; Claude Code and the bing-wm CLI are verified on the maintainer's host, the others are documented only.
Does IndexNow work with Google?
No. Google does not participate in IndexNow. The IndexNow registry lists Bing, Yandex, Seznam, Naver, Yep, Internet Archive and Amazonbot, and submission through api.indexnow.org fans out to participating engines.
How do I check if Bing has indexed my page?
Run bing-wm index url example.com https://example.com/page. Over MCP the bing_url_info tool reads the same data; HttpStatus 0 there means Bing reports no status, not 200.
Which parts of the Bing Webmaster API are covered?
The Microsoft interface has 62 methods: 59 are supported and three obsolete deep-link methods are excluded. Only the JSON API is used; SOAP, POX, the Bing Search API, Google Search Console and GA4 are out of scope.
Documentation pages
- bing-webmaster-ai-cli-mcpbing-webmaster-ai-cli-mcp gives an AI agent read access to what Bing knows about your sites — traffic, indexing, crawl issues, inbound links, keywords —…
- Working with Bing Webmaster Tools--- name: bing-webmaster description: Use when a task involves Bing Webmaster Tools, Bing indexing or crawl issues, Bing search traffic, submitting URLs…
- Bing Webmaster Tools API surfaceTranscribed from Microsoft's IWebmasterApi interface reference and each method's definition page, fetched 2026-08-25. The interface has 62 methods.…
- ConfigurationSettings come from environment variables. Secrets use SecretStr and are never written to plans or audit entries.
- OperationsCLI and MCP are thin facades over the same operation and planning modules. CLI commands accept --json; lists render as human-readable tables otherwise.
- Product boundariesThese are dated product decisions, not missing implementation work.