bing-seo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| B_CONFIRM | No | Require a confirm=true argument on mutating calls | false |
| B_LOG_FILE | No | Append log lines to a file (default: stderr only) | |
| B_READONLY | No | Block every mutating tool | false |
| B_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR | INFO |
| BING_API_KEY | No | Fallback API key for Bing Webmaster Tools (a saved key takes precedence) | |
| B_LOG_BODIES | No | Log request/response bodies to stderr | false |
| BING_MCP_CONFIG_DIR | No | Override the config directory | ~/.bing-seo-mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| b_auth_statusA | Show Bing auth status: whether an API key is configured and valid. |
| b_set_apikeyA | Save the Bing Webmaster Tools API key. Validated via GetUserSites before saving. Get it at Bing Webmaster Tools → Settings → API access → API Key. |
| bing_sites_getA | Bing: list all sites for the authenticated user. |
| bing_site_addC | Bing: add a site to the account. |
| bing_site_verifyA | Bing: trigger verification for a site (after placing the verification token). |
| bing_site_rolesC | Bing: get roles/owners of a site. |
| bing_submit_urlB | Bing: submit a single URL for indexing. |
| bing_submit_url_batchB | Bing: submit multiple URLs for indexing in one batch. |
| bing_submit_contentB | Bing: submit a URL together with its HTTP content (content submission API). |
| bing_url_quotaA | Bing: get daily/monthly URL submission quota for a site. |
| bing_sitemaps_getA | Bing: list submitted sitemaps/feeds for a site. |
| bing_sitemap_submitB | Bing: submit a sitemap/feed URL for a site. |
| bing_rank_traffic_statsC | Bing: get rank and traffic stats for a site. |
| bing_query_statsC | Bing: get search query stats for a site. |
| bing_page_statsC | Bing: get per-page traffic stats for a site. |
| bing_page_query_statsC | Bing: get query stats for a specific page. |
| bing_crawl_statsC | Bing: get crawl stats for a site. |
| bing_crawl_issuesB | Bing: get crawl issues (errors) for a site. |
| bing_keyword_getC | Bing: get impression/keyword data for an exact query. |
| bing_related_keywordsC | Bing: get related keywords for a query. |
| bing_blocked_urls_getB | Bing: list blocked URLs for a site. |
| bing_block_url_addC | Bing: block a URL or directory from Bing search. |
| bing_block_url_removeC | Bing: remove a URL block. |
| bing_deep_link_blockD | Bing: add a deep link block. |
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 24 tools
Each tool targets a specific operation (auth, site management, URL submission, sitemaps, stats, keywords, blocking) with clear boundaries. Even similar tools like submit_url, submit_url_batch, and submit_content are differentiated by their purpose and input.
Most tools follow a 'bing_<domain>_<action>' pattern, but there are minor inconsistencies: plural vs singular (bing_sites_get vs bing_site_add) and verb placement (bing_site_verify vs bing_verify? Actually consistent) but overall pattern is recognizable.
24 tools is on the higher end but justified by the broad scope of Bing Webmaster Tools (auth, sites, URLs, sitemaps, analytics, keywords, blocking). Each tool provides distinct functionality, so no obvious bloat.
The tool surface covers the full lifecycle of Bing SEO: authentication, site management (add, verify, roles), URL submission (single, batch, content), sitemaps, analytics, keywords, and blocking. Only minor gaps like site deletion or sitemap removal, but likely not supported by API.