How to Connect Bing Webmaster to Claude?

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 Claude plan that supports custom connectors.

1. 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. Copy it immediately — Bing only shows the full key once.

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

2. 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.

3. Add SourcetoMCP as a connector in Claude

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. 2In Claude, open Settings, then Connectors (Custom Connectors if you're on the beta).
3. 3Select Add connector, then paste in your server address.
4. 4The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects automatically.

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.

4. Ask Claude about your Bing Webmaster Tools site

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

1. 1What has my organic search performance on Bing looked like over the last month?
2. 2Are there any crawl issues Bing has flagged for my site?
3. 3Find keyword opportunities related to [topic] using Bing's own search data.
4. 4Check my sitemap's status, and resubmit it if 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. Claude 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.

Claude doesn't show a Connectors option: custom connectors currently roll out by plan; check your Claude plan or the Custom Connectors beta if you don't see it.

Claude says it can't find the tool or has no data: reopen the connector in Claude's Settings and confirm it still shows as connected; if not, 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 Claude's access entirely from the Connect an agent page. In Claude, remove the connector from Settings → Connectors. 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].