bing-webmaster-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BING_API_KEY | No | The API key. Overrides BING_API_KEY_FILE. | |
| BING_SITE_URL | No | Default site for every site-scoped tool, as registered in Bing Webmaster Tools. | |
| BING_API_KEY_FILE | No | Path to a file containing the API key. Relative paths resolve from the process working directory. | |
| INDEXNOW_KEY_FILE | No | Path to your local copy of the IndexNow key file (<key>.txt). | |
| INDEXNOW_SITE_URL | No | The host that serves the key file, when it differs from BING_SITE_URL (e.g. property on the apex, site served on www). Governs the indexnow tool's origin check and key location. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List the sites this Bing Webmaster Tools API key can access, with verification status. |
| query_statsA | Top search queries on Bing for the site: impressions, clicks and average position over the trailing period the API serves (~6 months). |
| page_statsB | Top pages by Bing search traffic for the site (impressions and clicks per page). |
| rank_traffic_statsC | Daily Bing impressions and clicks trend for the whole site. |
| crawl_statsA | Bingbot crawl activity over time: pages crawled, in-index counts, HTTP code buckets (2xx/301/302/4xx/5xx), robots.txt blocks and crawl errors. |
| crawl_issuesC | Concrete URLs with crawl issues Bing found on the site (HTTP errors, robots blocks, malware flags), with their HTTP code. |
| list_sitemapsB | Sitemaps Bing knows for the site, with processing status, URL counts and last-crawl time. |
| submit_sitemapB | Submit (or resubmit) a sitemap URL for the site. |
| remove_sitemapA | Remove a submitted sitemap from the site in Bing Webmaster Tools (does not delete the file). |
| url_infoB | What Bing knows about one URL of the site: discovery date, last crawl date, HTTP status and document details. |
| submit_urlsA | Push up to 500 URLs of the site into Bing's crawl queue (SubmitUrlBatch). The response includes the remaining daily/monthly submission quota. URLs must belong to the site. |
| indexnowA | Ping the IndexNow network (Bing, Yandex, Seznam, Naver…) that URLs of the site were added or updated — instant and quota-free. Requires the key file .txt to be hosted at the site root. |
| keyword_researchA | Bing search-impression volume for a keyword over a date range — real numbers, no credentials beyond the API key. With |
| backlinksA | Inbound links Bing knows for the site: without |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct resource or report dimension: query stats vs page stats vs daily trend, crawl stats vs crawl issues, sitemap lifecycle vs URL submission. Even the two URL-submission tools, submit_urls and indexnow, are clearly separated by mechanism and quota behavior.
Names are split between verb-led actions like list_sites and submit_sitemap and noun-led reports like page_stats, crawl_issues, url_info, and backlinks. All are snake_case and readable, but there is no single consistent verb_noun pattern.
14 tools cover the major Bing Webmaster workflows without redundancy; each one addresses a separate reporting or management need. This sits comfortably in the well-scoped 3-15 tool range.
The server covers traffic analytics, crawl health, sitemaps, URL submission/IndexNow, keyword research, and backlinks, so most SEO workflows are supported. The main gap is site administration: there is no way to add/remove a site or complete verification, only to list sites and their verification status.