Skip to main content
Glama
stufently

Bing Webmaster MCP Server

Related Servers

Alternatives to Bing Webmaster MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      59 npm
      1
      MIT
    • 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
    • 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
    • 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
    • A
      license
      Not graded
      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.
      2
      MIT
    • 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
      31 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 62 tools

    Disambiguation3/5

    The plan tools are clearly separated by action+noun names, and most read tools cover distinct endpoints. However, several read tools differ only by singular/plural or near-identical suffixes (traffic_queries vs traffic_query, traffic_pages vs traffic_page, url_info vs url_traffic_info), and all the plan tools share identical descriptions, leaving names as the only distinguishing signal. This creates real ambiguity for an agent choosing among them.

    Naming Consistency3/5

    All tools share the bing_ prefix and underscore separation, but the read tools do not follow a consistent verb_noun pattern; examples include bing_sites_list, bing_sitemap_details, bing_traffic_queries, and bing_keyword_stats. The plan tools are much more uniform with bing_plan_<verb>_<noun>, so the overall suite is mixed rather than fully consistent.

    Tool Count2/5

    With 62 tools, the server is far beyond the ideal 3-15 range and even the 25-tool threshold. The large number likely creates substantial context, token, and selection overhead for an agent. While each tool may map to a distinct Bing Webmaster API endpoint, the overall tool surface feels excessive for a focused MCP server.

    Completeness4/5

    The server covers a broad set of Bing Webmaster domains: site management, roles, traffic, URLs, crawl data, sitemaps, keywords, links, and plan-based modifications. The read side is especially thorough, and the plan tools give a coherent path for requesting changes via human-approved CLI commands. The main omissions are direct sitemap or feed editing and any actual apply/execute tool, but these appear intentional or minor.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues