Skip to main content
Glama
parthguru

Bing Webmaster Tools MCP Server

by parthguru

Related Servers

Alternatives to Bing Webmaster Tools MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      B
      quality
      B
      maintenance
      Enables AI agents to query Bing Webmaster Tools for traffic, indexing, crawl issues, inbound links, and keywords, and to safely plan state-changing operations like URL and IndexNow submissions through a reviewable two-step workflow.
      62
      MIT
    • A
      license
      B
      quality
      B
      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
      146 npm
      1
      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
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Google Search Console, Bing Webmaster Tools, and PageSpeed Insights, allowing queries for analytics, sites, sitemaps, inspections, crawl issues, and page speed analysis via natural language.
      816 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access Google Search Console search performance and index health data, including clicks, impressions, rankings, URL inspection, and sitemap management.
      9 npm
      MIT

    TDQS

    C2.1/5.0

    Scored across 34 tools

    Disambiguation1/5

    Many tools have heavily overlapping purposes, such as get_keyword_stats, get_keyword_data, get_related_keywords, get_query_stats, get_query_page_stats, get_query_page_detail_stats, get_page_query_stats, and get_query_traffic_stats. An agent would struggle to choose the correct tool without deep knowledge of the API's internal distinctions.

    Naming Consistency2/5

    All tools follow a get_ prefix, which is consistent, but the suffixes are unpredictable: info, stats, details, data, and settings are used interchangeably. The naming also swaps word order in confusing ways, e.g., get_page_query_stats vs get_query_page_stats, making the pattern unreliable.

    Tool Count2/5

    34 tools is excessive for a coherent MCP server surface, especially since almost all of them are read-only variations on the same underlying domain. The large count increases selection difficulty without providing meaningful functional variety.

    Completeness1/5

    The server is almost entirely read-only: every tool begins with get_, and there are no tools for submitting URLs, blocking/unblocking URLs, managing feeds, updating crawl settings, or handling site moves. This creates major dead ends for common Webmaster Tools workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues