SourcetoMCP
← Back to articles

How to Connect Bing Webmaster Tools to Grok?

Published September 27, 2026 · Written by Aanart

Illustrated lantern-lit pavilion on a frozen turquoise lake framed by an ice cave, with a stone bridge and snow-capped peaks at sunrise.

Contents

  1. 1Before you start
  2. 2Generate an API key in Bing Webmaster Tools
  3. 3Connect Bing Webmaster Tools to SourcetoMCP
  4. 4Add SourcetoMCP as a custom connector in Grok
  5. 5Ask Grok about your Bing Webmaster Tools site
  6. 6A note on write actions
  7. 7Troubleshooting
  8. 8Revoking access
  9. 9Still stuck?

Bing Webmaster Tools connects differently to Google Search Console: instead of signing in through a consent screen, you generate an API key inside Bing Webmaster Tools and paste it in. From there it's the same two-part setup as every other source: link Bing Webmaster Tools to SourcetoMCP, then add SourcetoMCP itself as a custom connector inside Grok. For what the connector covers, see the Bing Webmaster Tools MCP server page.

Before you start

You'll need a SourcetoMCP account with at least one brand created, a Bing Webmaster Tools account with at least one verified site, and a Grok account. Custom connectors on grok.com need a SuperGrok plan, either standalone or through X Premium+. On a Grok Business or Enterprise seat, a team admin provisions the connector instead, see the note in the next section.

Generate an API key in Bing Webmaster Tools

  1. 1Sign in at bing.com/webmasters with the Microsoft account tied to your site.
  2. 2Make sure the site you want to connect is already added and verified.
  3. 3Click your profile icon (top right) → Settings → API Access.
  4. 4Select Generate API Key, then copy it immediately, because Bing only shows the full key once.

One key covers every site your account can see, and you'll pick which sites to connect in the next step.

Connect Bing Webmaster Tools to SourcetoMCP

  1. 1From your dashboard, go to Connectors → Add a connection.
  2. 2Find the Bing Webmaster Tools card and select Connect.
  3. 3Paste the API key into the field and select Connect Bing Webmaster Tools. This verifies the key directly against Bing.
  4. 4Choose which verified site(s) to connect, then confirm.

Connected sites then appear on your Connections page like any other source.

Add SourcetoMCP as a custom connector in Grok

  1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
  2. 2Go to grok.com/connectors and select New Connector.
  3. 3Choose Custom and paste in your server address.
  4. 4Complete the authentication step so Grok can reach it. SourcetoMCP runs its own OAuth, so there is no client ID or secret to enter.
  5. 5Approve access when Grok asks for it, the same as you would for any other connector.

On a Business or Enterprise plan, a team admin adds the connector first, from console.x.ai's Grok Business → Connectors, choosing Add Connector, then Other, and pasting the same server address. Each team member then opens grok.com/connectors themselves and signs in with their own SourcetoMCP account, so a person only ever reaches the sources their own account can see.

Once approved, the connection appears under Active connections on the Connect an agent page in SourcetoMCP, so you can see exactly what has access at any time.

Ask Grok about your Bing Webmaster Tools site

Once it's added, SourcetoMCP is available to Grok in any conversation, there is no separate toggle to switch on per chat. Grok discovers the tools the server exposes and calls them the same way it uses any of its built-in connectors.

With both pieces connected, Grok can query your Bing search performance, look at who links to your pages, check crawl health, research keywords using Bing's own search data, and act on what it finds if you ask. Try something like:

  1. 1Compare my Bing organic clicks quarter over quarter.
  2. 2Which referring domains link to my site the most right now?
  3. 3Are there any crawl errors Bing has flagged this week?
  4. 4Resubmit my sitemap if Bing shows it's failing.

The first three are read-only reports. The last one is a write action. See the note below on how SourcetoMCP handles those.

A note on write actions

Bing Webmaster Tools through SourcetoMCP can do two things beyond reporting: ask Bing to recrawl a URL (one at a time or in a batch), and submit or remove a sitemap. Neither changes anything on your actual site, and neither can affect spend or take content offline the way a write action on an ads connector can. The worst case is a wasted submission against Bing's own daily quota. Grok will still tell you what it's about to do before it does it.

Troubleshooting

“That API key was rejected”: the key is wrong, was regenerated since you copied it, or was revoked. Generate a fresh one under Settings → API Access and try again.

My site isn't in the list when connecting: the account the key belongs to hasn't added or verified that site in Bing Webmaster Tools yet. Add and verify it there first, then reconnect.

New Connector → Custom isn't available on grok.com: custom connectors need a SuperGrok plan on an individual account. On a Business or Enterprise seat, a team admin has to provision the connector first from console.x.ai before it shows up for anyone else.

Grok says it can't find the tool or has no data: check the connector still shows as connected under grok.com/connectors. If it does, confirm the connection still shows under Active connections in SourcetoMCP, then remove and re-add it to trigger a fresh approval.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the site from your Connections page, or revoke Grok's access entirely from the Connect an agent page. In Grok, open grok.com/connectors and remove it. On Business and Enterprise, a team admin removes it for everyone from console.x.ai. In Bing Webmaster Tools, generate a new API key under Settings → API Access, which invalidates the old one.

Still stuck?

Reach us at [email protected].