Skip to content
HOSTED MCP · BING OAUTH · READ-ONLY

Bing Webmaster Tools
MCP server.

Bring Bing search into the conversation.

Read your verified sites’ Bing Webmaster data from your AI client. Investigate search traffic, query performance and crawl trends alongside the evidence behind each recommendation. The hosted Bing Webmaster Tools MCP server needs no API keys, no local process and no cloud project: paste one endpoint, sign in with Bing, and ask.

Remote MCP endpointhttps://mcp.liftaven.com/bing
Connect your AI client ↗

Your data. Better questions.

Explore search performance

List your sites and read Bing traffic, query and page statistics. Keep Bing results separate from Google Search Console metrics.

Investigate crawling

Read crawl statistics to identify patterns worth investigating. A crawl signal is a starting point for diagnosis, not proof of a ranking problem.

Review sitemap coverage

List sitemaps and explicitly submit a sitemap when needed. Submission does not guarantee crawling, indexing or ranking.

Connect in three steps

  1. Add a remote MCP server. Use an AI client with remote HTTP MCP and OAuth support. Client availability and plan requirements vary.
  2. Paste your endpoint. Use https://mcp.liftaven.com/bing. Start the connection from your AI client, rather than opening the endpoint as a normal web page.
  3. Authorise with Bing. Review the requested access, finish consent and return to your client. Ask it to list your accessible properties or sites first.

Your first conversation

After consent, check that your client lists the server’s tools. Start by listing sites or properties, choose the correct one, then ask a question with an explicit date range. Ask the agent to include the source, dates and any missing data in its answer.

If the connection does not work

A 401 response when opening the endpoint in a browser is expected: connect from your MCP client so it can start OAuth. If your property is missing, check that you authorised the Bing account with access to it. If consent expires, reconnect through your client. If the client does not support remote MCP with OAuth, use a compatible client rather than pasting access tokens.

You do not need to create your own OAuth app or paste a provider token. The client receives a scoped MCP connection. You can revoke access when you no longer need it.

Set up the Bing MCP server in your client

Every client below supports remote HTTP MCP with OAuth. Add the server, start the connection, finish Bing consent in the browser and return to the client. The server name is yours to choose; liftaven-bing is used in the examples.

Claude (web and desktop)

Open Settings, choose Connectors, then Add custom connector. Paste https://mcp.liftaven.com/bing as the remote MCP server URL and save. Click Connect on the new connector to start Bing sign-in. Availability depends on your Claude plan and organisation settings.

Claude Code

Run the command below in your terminal, then type /mcp inside Claude Code to authenticate.

claude mcp add --transport http liftaven-bing https://mcp.liftaven.com/bing

Cursor

Add the entry below to .cursor/mcp.json in your project, or to the global MCP settings. Cursor opens the browser for OAuth the first time the server is used.

{
  "mcpServers": {
    "liftaven-bing": {
      "url": "https://mcp.liftaven.com/bing"
    }
  }
}

VS Code (GitHub Copilot agent mode)

Create .vscode/mcp.json with the entry below, then start the server from the MCP view.

{
  "servers": {
    "liftaven-bing": {
      "type": "http",
      "url": "https://mcp.liftaven.com/bing"
    }
  }
}

ChatGPT and other clients

Use the client’s custom connector or remote MCP option where the plan allows it, and paste the same URL. If a client only supports local stdio servers, a bridge such as mcp-remote can forward to the hosted endpoint; native remote support is preferable when available.

What the Bing MCP tools return

Each tool returns a bounded, labelled report rather than a raw API dump, so an agent can cite the property, window and definitions it used.

list_sites

Sites in your Bing Webmaster account and whether each is verified.

get_traffic

Daily clicks and impressions with totals over 7, 28, 90 or 180 days.

get_query_stats / get_page_stats

Ranked query and page breakdowns with separate click and impression positions.

get_crawl_stats

Bingbot activity, HTTP status groups, robots.txt blocks and crawl errors, plus indexed-page and inbound-link snapshots.

list_sitemaps

Sitemap and feed submissions Bing knows about, with type, status and URL counts.

submit_sitemap

The only write: register or re-submit a sitemap you confirm.

Start with a useful question

Example prompts. Your agent’s answers depend on the data and permissions available.

List my verified Bing Webmaster sites.
For my website, summarise the available query and page performance. Include the reporting window.
Check my crawl statistics and sitemaps. Which changes should I investigate first?
Compare my Bing clicks with my Google Search Console clicks for the same 28 days, keeping the two sources separate.

Hosted Bing MCP server vs running your own

Open-source Bing Webmaster Tools MCP servers on GitHub work well for developers who are comfortable creating API credentials and running a local process. The hosted endpoint trades that control for a two-minute setup and nothing to maintain.

ConsiderationSelf-hosted open-source serverLiftaven hosted endpoint
SetupCreate a cloud project or app registration, enable APIs, generate credentials, install and run locallyPaste one URL into your client and sign in with Bing
CredentialsStored on your machine; you rotate and secure themOAuth tokens held server-side, scoped to read access; revoke from your provider account at any time
Works fromThe computer running the processAny client on any device, including web-based clients
Write accessDepends on the project; some expose write toolsRead-only, plus an explicit sitemap submission you confirm
Reporting limitsRaw API limitsBounded reports with labelled windows and row caps
CostFree software; your time to set up and maintainFree, with no Liftaven subscription required

Both approaches read the same provider data. Choose self-hosting if you need custom tools or an air-gapped setup; choose the hosted endpoint if you want your team using Bing data in their AI client this afternoon.

Access and limits

The standalone Bing MCP has no Liftaven subscription gate. Bing permissions, API availability and per-tool bounds still apply. This is a Webmaster Tools connection, not a general Bing web-search API.

Your AI client receives the reports it requests. Review its data policies before connecting. Read Liftaven’s privacy and permissions.

Bing Webmaster Tools MCP server: questions, answered

Is this a Bing search engine MCP?

It reads your own sites’ Bing Webmaster Tools data. It does not search the public web or return general search results.

Can it submit my sitemap?

Yes, through an explicit sitemap-submission request for an authorised site. Submission is not a guarantee that Bing will index the URLs.

Do I need a Bing API key?

No. Authorise with the Microsoft account that owns the Webmaster Tools site. The hosted server handles the OAuth flow; you never paste an API key into your client.

Why does Bing report two positions?

Bing reports a separate average click position and average impression position. Do not collapse them into one rank.

Does Bing include Copilot traffic?

Bing’s traffic series includes supported search verticals and Copilot or Chat traffic where Bing includes it in that report. The server passes the figures through as reported.

Can I use it alongside the Google Search Console server?

Yes. Add both endpoints to the same client, or sign into Liftaven and use the unified endpoint. Keep Bing and Google figures separate; they come from different indexes.

Which clients are supported?

Any client with remote HTTP MCP and OAuth support: Claude, Claude Code, Cursor, VS Code and ChatGPT plans that allow custom connectors.

Need all your SEO data together?

The unified Liftaven MCP uses https://mcp.liftaven.com/mcp. Sign into Liftaven and approve your client to reuse the connections in your dashboard. Standalone provider endpoints have their own consent.