A Model Context Protocol server that lets Claude (and any MCP client) drive Bing Webmaster Tools end to end — manage and verify sites, push URLs for indexing, submit sitemaps, pull traffic / query / crawl stats, research keywords, and block URLs. Auth is a single API key — paste it once and you're running.

✨ Highlights

• 🌐 Sites & verification — list, add, verify, inspect roles
• 📤 URL submission — single, batch, full-content, with live quota
• 🗺️ Sitemaps — list and submit feeds
• 📈 Stats — rank & traffic, queries, pages, crawl stats & issues
• 🔑 Keyword research — keyword and related-keyword data
• 🚫 URL blocking — block pages/directories and deep links
• 🔐 One-key auth — validated on save, stored locally
• 🛡️ Safety rails — read-only mode and per-call confirm guards

📦 Installation

Run straight from npm with npx (no install needed), or build from source:

# from source
git clone https://github.com/skiddgoddamn/bing-seo-mcp
cd bing-seo-mcp
npm install && npm run build

🔌 Connect to your MCP client

Add to your MCP config (e.g. ~/.claude.json or claude_desktop_config.json):

{
  "mcpServers": {
    "bing-seo": {
      "command": "npx",
      "args": ["-y", "bing-seo-mcp"],
      "env": { "BING_API_KEY": "" }
    }
  }
}

{
  "mcpServers": {
    "bing-seo": {
      "command": "node",
      "args": ["F:/projects/bing-seo-mcp/build/index.js"]
    }
  }
}

🔑 Get your API key

1. Sign in at Bing Webmaster Tools
2. Go to Settings → API access → API Key
3. Copy the key — set it via the b_set_apikey tool or the BING_API_KEY env var

🚀 Setup flow

⚙️ Environment variables

See .env.example for a ready-to-copy template.

🧰 Tool reference

🔐 Auth

🌐 Site management

📤 URL submission

🗺️ Sitemaps

📈 Stats & analytics

🔑 Keywords

🚫 URL blocking

🛡️ Safety rails

• B_READONLY=true — blocks every tool whose name contains _add _submit _remove _block _verify. Reads still work.
• B_CONFIRM=true — mutating tools return a preview and require a follow-up call with confirm: true.

📄 License

MIT © skiddgoddamn