Skip to main content
Glama
Bing Webmaster Tools MCP

Bing Webmaster Tools MCP

Related Servers

Alternatives to Bing Webmaster Tools MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to query Google Search Console performance data, inspect URL indexing status, submit URLs via IndexNow, and check title and meta-description lengths against Bing limits directly in chat.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Bing Webmaster Tools and IndexNow for AI agents: traffic, indexing, crawl issues, inbound links, keywords. Direct writes are off by default; changes go through a plan a person applies.
      63
      56 PyPI
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other MCP clients to read Google Search Console and Bing Webmaster Tools data, analyze query/page performance, compare periods, inspect indexing and canonical status, and retrieve sitemap and keyword statistics.
      23
      59 npm
      MIT
    • 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
      10 npm
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Connects Claude to Google Search Console, GA4, Bing Webmaster Tools, IndexNow, PageSpeed Insights, AdSense and Google Ads Keyword Planner, plus live technical SEO audits of pages and sitemaps. Users ask plain-language questions about traffic drops, index status, canonicals, AI referral traffic and keyword volumes, and answers are pulled live from the APIs in real time.
      28
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Google Search Console data, including search analytics, indexing status, and sitemap management, through natural language conversations with Claude.
      155 npm
      6
      MIT

    TDQS

    A3.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target a clearly distinct dimension (queries, pages, crawls, links, sitemaps, trends), and descriptions explicitly disambiguate the risky pairs like get_query_stats vs get_queries_for_page and get_page_stats vs get_pages_for_query. The only mild overlap is get_inbound_links vs get_inbound_link_counts (per-URL link detail vs per-page counts) and get_url_info vs get_url_traffic_info, but both pairs are still distinguishable from their descriptions.

    Naming Consistency5/5

    Every tool follows a consistent verb_noun snake_case pattern, overwhelmingly get_* with a single list_sites. The noun phrases are descriptive and predictable across the whole set.

    Tool Count4/5

    17 tools is slightly above the ideal range for a single-domain server, but the domain (a full webmaster analytics API) is broad and each tool maps to a distinct report or entity. None feel like filler, so it justifies its weight without being bloated.

    Completeness4/5

    Coverage is strong across analytics (queries, pages, trends), crawl diagnostics, sitemaps, links, and keyword research. The main gap is action-oriented operations like URL submission and sitemap submission: get_url_submission_quota hints at submission but no submit tool exists, leaving a write-side dead end.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data