Skip to main content
Glama
Sign In
Bing Webmaster MCP Server

Bing Webmaster MCP Server

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Bing Webmaster MCP Server

No user-submitted related servers found.

    Related Servers

    • bing-seo-mcp

      skiddgoddamn
      A
      license
      B
      quality
      C
      maintenance
      Provides AI agents full access to Bing Webmaster Tools API for site management, URL submission, sitemaps, traffic stats, keyword research, and URL blocking.
      24
      21 npm
      1
      MIT

    • mcp-server-bwt

      agalliani
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to manage Bing Webmaster Tools, including site verification, URL submissions, traffic analytics, crawl monitoring, and keyword analysis through natural language.
      62
      MIT

    • seo-webmaster-mcp

      itsaakashpatel
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to access search analytics from Google Search Console and Bing Webmaster Tools, inspect URL indexing, monitor sitemaps, and submit URLs to search engines via IndexNow.
      7
      MIT

    • Bing Webmaster Tools MCP

      parthguru
      A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to query Bing Webmaster Tools data such as site verification, traffic analytics, and search performance, with read-only defaults and configurable site access controls.
      34
      MIT

    • Bing Webmaster Tools MCP

      rafavillaplana
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to query Bing Webmaster Tools performance, crawl, sitemap, backlink, and keyword data in plain language through the official Bing Webmaster API. It is read-only and runs locally using your own API key.
      17
      29 npm
      2
      MIT

    • Google Search Console MCP

      thenavidm
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query and analyze Google Search Console data, including search analytics, URL inspection, sitemaps, and property verification, and to perform actions like submitting sitemaps and adding properties through natural language.
      19
      26 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 63 tools

    Disambiguation4/5

    Descriptions are exceptionally explicit, each carrying 'Do not use this; call X instead' cross-references that sharply separate near-neighbors (bing_traffic_query vs bing_traffic_queries, bing_query_page_stats vs bing_query_page_detail_stats, add vs remove plan pairs). With 63 tools, however, several singular/plural and detail/list pairings remain easy to misselect despite the guidance.

    Naming Consistency4/5

    All tools use a consistent bing_ snake_case prefix, which is a strong, predictable foundation. Ordering is not uniform, though: some are noun_then_action (bing_sites_list, bing_plan_list) while others are action_then_noun (bing_plan_add_blocked_url, bing_plan_submit_url), and many are noun-only (bing_url_info, bing_link_counts), so the pattern is readable but not fully systematic.

    Tool Count2/5

    At 63 tools the surface is very heavy for a single server, far above the 25+ threshold. Much of the bloat comes from the deliberate read+plan pairing (every mutating operation has a matching bing_plan_* recorder), which roughly doubles the endpoint count and could be consolidated.

    Completeness4/5

    Read coverage of the Bing Webmaster domain is broad (sites, crawl, traffic/query/page stats, links, sitemaps, blocks, quotas, keywords, roles) and write intents are represented as reviewable plans across nearly every mutating operation. The one structural gap is that no tool applies a plan, so the write lifecycle dead-ends at the MCP boundary and must be finished via CLI/human.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources