# Bing Webmaster AI CLI MCP [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/stufently/bing-webmaster-ai-cli-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bing-webmaster-ai-cli-mcp

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "bing-webmaster-ai-cli-mcp": {
    "command": "uvx",
    "args": ["bing-webmaster-ai-cli-mcp"],
    "env": {
      "BING_WM_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `BING_WM_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Bing Webmaster AI CLI MCP does

Bing Webmaster AI CLI MCP MCP server exposes Bing Webmaster Tools data to AI clients over MCP and also provides the `bing-wm` command-line interface. It can inspect site traffic, indexing status, crawl problems, inbound links, keywords, and other data available through the JSON Bing Webmaster Tools API. It also supports protocol-compliant IndexNow submission. SOAP and POX interfaces are not included.

The package includes 34 Bing read tools, a local read-only tool for planning an IndexNow key operation, plan inspection, and write-related tools. Typical questions include which pages Bing cannot crawl, whether a URL is indexed, and how search performance changed during a period.

## How it works

The server runs as a stdio MCP process. AI clients invoke read tools immediately. Operations that change Bing state follow a separate write policy controlled by `BING_WM_ALLOW_WRITES`.

With the default value of `false`, the server exposes planning tools such as `bing_plan_<operation>`. These create durable local plan records but do not contact Bing to apply the change. A human reviews and applies a plan through the CLI with `bing-wm plan apply`. With `true`, the server instead exposes direct `bing_<operation>` tools that create and apply a plan in one call.

Both modes record plans and append audit entries. Plans are one-shot and expire, and local controls include a site denylist and restart-persistent daily write limits. If a process stops while holding a plan lock, `bing-wm plan unlock PLAN_ID` checks that the recorded process has exited before recovery. An unfinished operation is marked with an unknown outcome and cannot be applied again.

## Setup and configuration

Bing Webmaster AI CLI MCP MCP server requires an API key created in Bing Webmaster Tools under Settings → API Access. Set it in `BING_WM_API_KEY`; keep the value in a user-level client configuration rather than a committed project file.

The simplest installation starts the stdio server with `uvx bing-webmaster-ai-cli-mcp`. The package is also available through pip, pipx, and PyPI. Python 3.12, 3.13, and 3.14 are supported. `uvx` can use the latest published package, a pinned release, or the repository source.

Set `BING_WM_ALLOW_WRITES=false` for reviewed changes, or set it to `true` only when the agent is trusted to modify the Bing account directly. Restart the MCP process after changing this setting so the client refreshes its tool list.

## Tools and capabilities

- Query Bing Webmaster traffic and search data.
- Inspect indexing and crawl information.
- Review inbound links, keywords, and site-related reports.
- Submit URLs through IndexNow.
- Create, inspect, apply, unlock, and audit local write plans through the CLI.
- Choose between reviewed plans and direct write tools.

The server does not expose an MCP tool for applying or rejecting a plan; those actions remain CLI operations. Direct writes are not idempotent, so a lost response should be checked against the audit log or plan list before retrying.

## Limitations and notes

Bing's submission quota still applies. The default configuration is read-only toward Bing, but changing the write setting alters the advertised tool set and the level of agent access. The project documents configurations for Claude Desktop, Cursor, Windsurf, and Zed, while the README identifies Claude Code as verified and Codex as configured but not separately checked. Other client and operating-system combinations may not have been tested. The API key and local plan and audit files should be protected as account-sensitive data.

_Full upstream README: https://allmcps.com/mcp/bing-webmaster-ai-cli-mcp/readme_