Bing Webmaster AI CLI MCP

bing-webmaster-ai-cli-mcp

bing-webmaster-ai-cli-mcp gives an AI agent read access to what Bing knows about your sites — traffic, indexing, crawl issues, inbound links, keywords — and a write path you choose: reviewed plan-and-apply by default, or direct writes when you opt in.

It ships a Python 3.12+ CLI and MCP server for the JSON Bing Webmaster Tools API, plus protocol-correct IndexNow submission. SOAP and POX are deliberately absent.

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_ 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_ 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.

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.

Verified clients and platforms

Only what has actually been run is listed as verified. Everything else in Add the MCP server to your AI client is a documented config that nobody has checked end to end.

Add the MCP server to your AI client

Every JSON block below runs the same uvx command as Install. BING_WM_ALLOW_WRITES is false here (the default, spelled out), so writes are planned and you apply them. Set it to true for direct writes — see Choosing a write path. Keep the key in a user-level config, not in a project file you commit. The server exposes 34 Bing read tools, one local read-only tool (bing_indexnow_key_plan), plan inspection, and one write tool per supported operation — bing_plan_ tools by default, or direct bing_ tools when BING_WM_ALLOW_WRITES=true. It exposes no plan application or rejection tool. Restart the server after changing the setting so the client refreshes its tool list.

Claude Code

Project file: .mcp.json in the project root.

{

"mcpServers": { "bing-webmaster": { "command": "uvx", "args": [ "bing-webmaster-ai-cli-mcp" ], "env": { "BING_WM_API_KEY": "your-api-key", "BING_WM_ALLOW_WRITES": "false" } } } }

Or from the terminal:

claude mcp add bing-webmaster --scope user \

--env BING_WM_API_KEY=your-api-key --env BING_WM_ALLOW_WRITES=false \ -- uvx bing-webmaster-ai-cli-mcp

Claude Desktop

File: claude_desktop_config.json — macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json, Linux ~/.config/Claude/claude_desktop_config.json.

{

"mcpServers": { "bing-webmaster": { "command": "uvx", "args": [ "bing-webmaster-ai-cli-mcp" ], "env": { "BING_WM_API_KEY": "your-api-key", "BING_WM_ALLOW_WRITES": "false" } } } }

One click, without editing JSON: download the .mcpb from https://github.com/stufently/bing-webmaster-ai-cli-mcp/releases/latest and open it. Claude Desktop installs the extension and asks for the API key. Direct writes stay off unless you turn Allow direct writes on. While they are off the extension only records plans. Applying one needs the bing-wm CLI, which the extension does not put on your PATH: install it with pip as in Install, export the same key as BING_WM_API_KEY in that shell, then run bing-wm plan apply.

The release includes checksums.txt with the SHA256 of every .mcpb. Download that file into the same directory as the bundle and check it before opening the extension:

sha256sum -c --ignore-missing checksums.txt   # run next to the downloaded .mcpb

On macOS, filter the bundle's line and check it with shasum -a 256 -c -.

Releases from the next tag on also carry a GitHub build provenance attestation for each .mcpb, signed in the release workflow. Check that a bundle was built by this repository's workflow and not swapped afterwards (needs the GitHub CLI):

gh attestation verify <bundle>.mcpb --repo stufently/bing-webmaster-ai-cli-mcp

Cursor

After installing, replace the placeholder values in ~/.cursor/mcp.json. Or add the block below by hand.

File: ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this project).

{

"mcpServers": { "bing-webmaster": { "command": "uvx", "args": [ "bing-webmaster-ai-cli-mcp" ], "env": { "BING_WM_API_KEY": "your-api-key", "BING_WM_ALLOW_WRITES": "false" } } } }

Windsurf

File: mcp_config.json — macOS and Linux ~/.config/devin/mcp_config.json (or $XDG_CONFIG_HOME/devin/mcp_config.json), Windows %APPDATA%\devin\mcp_config.json. Older builds read ~/.codeium/windsurf/mcp_config.json.

{

"mcpServers": { "bing-webmaster": { "command": "uvx", "args": [ "bing-webmaster-ai-cli-mcp" ], "env": { "BING_WM_API_KEY": "your-api-key", "BING_WM_ALLOW_WRITES": "false" } } } }

Zed

File: settings.json — Linux and macOS ~/.config/zed/settings.json.

{

"context_servers": { "bing-webmaster": { "command": "uvx", "args": [ "bing-webmaster-ai-cli-mcp" ], "env": { "BING_WM_API_KEY": "your-api-key", "BING_WM_ALLOW_WRITES": "false" } } } }

An optional Streamable HTTP entry point is also available once the package is on PATH (the pip install above; uvx does not install a lasting command):

export BING_WM_HTTP_BEARER_TOKEN='a-random-token-of-at-least-32-characters'

bing-webmaster-ai-cli-mcp-http

It refuses non-loopback bind add