Microsoft Advertising (Bing Ads) runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Oct 2026.
Microsoft Advertising (Bing Ads) MCP server: 20 read tools, 23 opt-in preview-first writes.
Today is the operative word: we check Microsoft Advertising (Bing Ads) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add bing-ads -e 'BING_ADS_CLIENT_ID=<BING_ADS_CLIENT_ID>' -e 'BING_ADS_REFRESH_TOKEN=<BING_ADS_REFRESH_TOKEN>' -e 'BING_ADS_ACCOUNT_IDS=<BING_ADS_ACCOUNT_IDS>' -- npx -y @getmcpads/bing-ads-mcp-server
{
"mcpServers": {
"bing-ads": {
"command": "npx",
"args": [
"-y",
"@getmcpads/bing-ads-mcp-server"
],
"env": {
"BING_ADS_ACCOUNT_IDS": "<BING_ADS_ACCOUNT_IDS>",
"BING_ADS_CLIENT_ID": "<BING_ADS_CLIENT_ID>",
"BING_ADS_REFRESH_TOKEN": "<BING_ADS_REFRESH_TOKEN>"
}
}
}
}
[mcp_servers.bing-ads]
command = "npx"
args = ["-y", "@getmcpads/bing-ads-mcp-server"]
env = { BING_ADS_CLIENT_ID = "<BING_ADS_CLIENT_ID>", BING_ADS_REFRESH_TOKEN = "<BING_ADS_REFRESH_TOKEN>", BING_ADS_ACCOUNT_IDS = "<BING_ADS_ACCOUNT_IDS>" }
{
"mcpServers": {
"bing-ads": {
"command": "npx",
"args": [
"-y",
"@getmcpads/bing-ads-mcp-server"
],
"env": {
"BING_ADS_ACCOUNT_IDS": "<BING_ADS_ACCOUNT_IDS>",
"BING_ADS_CLIENT_ID": "<BING_ADS_CLIENT_ID>",
"BING_ADS_REFRESH_TOKEN": "<BING_ADS_REFRESH_TOKEN>"
}
}
}
}
{
"servers": {
"bing-ads": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getmcpads/bing-ads-mcp-server"
],
"env": {
"BING_ADS_ACCOUNT_IDS": "<BING_ADS_ACCOUNT_IDS>",
"BING_ADS_CLIENT_ID": "<BING_ADS_CLIENT_ID>",
"BING_ADS_REFRESH_TOKEN": "<BING_ADS_REFRESH_TOKEN>"
}
}
}
}
Put your own values in place of
<BING_ADS_CLIENT_ID> (Application (client) ID of your OAuth app registration), <BING_ADS_REFRESH_TOKEN> (Refresh token with the msads.manage and offline_access scopes. Kept in memory only), <BING_ADS_ACCOUNT_IDS> (Comma-separated allowed account IDs, optionally accountId:customerId. Required even for reads).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BING_ADS_DEVELOPER_TOKEN (Your developer token. Required in production; the sandbox uses the universal token), BING_ADS_CLIENT_SECRET (Client secret, only for a web app registration or Google identity), BING_ADS_CUSTOMER_ID (Customer ID that owns the accounts, unless every account entry carries its own), BING_ADS_ENVIRONMENT (production (default) or sandbox), BING_ADS_IDENTITY_PROVIDER (Microsoft (default) or Google, for users who sign in with Google), BING_ADS_OAUTH_TENANT (Microsoft Entra tenant for the token endpoint. Defaults to common), BING_ADS_ENABLE_WRITES (true exposes 23 write tools. Defaults to false. Writes preview until confirm:true).
Google Ads MCP server: 35 read tools, 13 opt-in preview-first writes.
Google Ads MCP server: 17 tools for reporting, campaigns, keywords, assets. Writes preview first.
MCP server for Microsoft Advertising (Bing Ads) — campaigns, keywords, and reports
Search Console MCP server: 8 tools for queries, traffic drops, indexing. Writes preview first.
Microsoft Ads MCP server: 11 tools for search, PMax, Google Ads imports. Read-only by default.
Google Search Console MCP server: 20 read tools, no write tools.
Google Analytics 4 MCP server: 27 read tools, no write tools.
GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools.
Answers built from our own checks of this server.