Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Bing Webmaster Tools MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Bing Search MCP Server

      Adityas7netapp
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides AI-grounded Bing search capabilities using the Azure AI Project Client. It enables intelligent web searches with automated citation tracking and URL extraction for seamless AI integration.
      -

    • Search Console MCP

      saurabhsharma2u
      A
      license
      B
      quality
      A
      maintenance
      Model Context Protocol (MCP) server that provides AI agents with access to Google Search Console data.
      25
      1,377 npm
      322
      MIT

    • crakseo-search-console

      CrakSEO
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query Google Search Console and Bing Webmaster Tools data for verified properties, covering clicks, impressions, CTR and rankings by query or page, URL index inspection, sitemap listing and submission, and Bing crawl issues and traffic stats. It runs as a hosted remote MCP server, so nothing is installed locally.
      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

    C2.7/5.0

    Scored across 62 tools

    Disambiguation2/5

    There are many near-identical analytics tools (get_query_stats, get_query_traffic_stats, get_query_page_stats, get_page_query_stats, get_page_stats, get_url_traffic_info) whose boundaries are subtle and likely to be confused. The CRUD groups are mostly clear, but the overlapping stats getters make tool selection hazardous.

    Naming Consistency4/5

    Almost all tools follow a clear verb_noun snake_case pattern (get_*, add_*, remove_*, submit_*). Minor inconsistencies like add_site_roles vs remove_site_role, get_query_page_stats vs get_page_query_stats, and get_deep_link_algo_urls keep it from being perfectly uniform.

    Tool Count2/5

    62 tools is far too many for a coherent MCP surface, even for a broad API; many analytics getters could be consolidated. The count heavily outweighs the typical 3-15 well-scoped set and will impose a large selection burden on agents.

    Completeness4/5

    The tool surface covers most Webmaster Tools workflows: site verification, roles, feed/URL submission, crawl stats/issues, traffic stats, blocks, and settings. Minor gaps like no remove_connected_page and some deprecated deep-link endpoints prevent a perfect score.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources