Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"bing-ads": {
"url": "http://localhost:3002",
"type": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Production-grade MCP server for Microsoft Advertising (Bing Ads) API. Enables Claude to manage Bing/Microsoft Ads accounts with full campaign, ad group, keyword, and performance analysis capabilities.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-bing-ads' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-bing-ads against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in marketing
DataForSEO API modelcontextprotocol server
一键同步文章到多个内容平台,支持今日头条、WordPress、知乎、简书、掘金、CSDN、typecho各大平台,一次发布,多平台同步发布。解放个人生产力
MCP server for the PostFast API — schedule and manage social media posts via AI tools
Google Ads MCP with MCC support: 35 tools for campaigns, keywords, reporting, GAQL.
MCP Security Weekly
Get CVE alerts and security updates for io.github.mharnett/bing-ads and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Production-grade MCP server for Microsoft Advertising (Bing Ads) API. Enables Claude to manage Bing/Microsoft Ads accounts with full campaign, ad group, keyword, and performance analysis capabilities.
Features:
Note: ⚠️ First open-source Bing Ads MCP with comprehensive tooling
npm install mcp-bing-ads
Security: Never share your .mcp.json file or commit it to git -- it may contain API credentials. Add .mcp.json to your .gitignore.
Get OAuth credentials:
Microsoft Advertising APIhttps://ads.microsoft.com/msads.manage offline_accessCreate config.json:
cp config.example.json config.json
Fill in your credentials:
{
"oauth": {
"client_id": "YOUR_AZURE_CLIENT_ID",
"client_secret": "YOUR_AZURE_CLIENT_SECRET"
},
"clients": {
"default": {
"customer_id": "YOUR_CUSTOMER_ID",
"account_id": "YOUR_ACCOUNT_ID",
"name": "My Account"
}
}
}
Set environment variables (recommended):
export BING_ADS_DEVELOPER_TOKEN="your_developer_token"
export BING_ADS_CLIENT_ID="your_client_id"
export BING_ADS_REFRESH_TOKEN="your_refresh_token"
# Optional:
export BING_ADS_CLIENT_SECRET="your_client_secret"
# Optional: opt into mutating tools (read-only by default)
export BING_ADS_MCP_WRITE="true"
| Variable | Required | Default | Description |
|---|---|---|---|
BING_ADS_DEVELOPER_TOKEN | yes | -- | Microsoft Advertising developer token |
BING_ADS_CLIENT_ID | yes | -- | Azure AD app client ID |
BING_ADS_REFRESH_TOKEN | yes | -- | OAuth refresh token |
BING_ADS_CLIENT_SECRET | no | -- | Azure AD app client secret (if confidential client) |
BING_ADS_MCP_WRITE | no | false | Set to true, 1, or yes to expose mutating tools (pause/update/add). Any other value -- or unset -- keeps the server read-only. |
Mutating tools (bing_ads_pause_keywords, bing_ads_update_campaign_budget, bing_ads_add_shared_negatives) are hidden from the tool list and refused at call time unless BING_ADS_MCP_WRITE=true is set in the server environment. This is a safety gate against casual write actions -- for example, pausing a keyword or editing a budget based on a throwaway chat message. To make write changes, set the env var explicitly in your .mcp.json or shell profile for the session that needs it, then unset it afterwards. Read tools (list/report/performance) are always available.
npm start
Add to ~/.claude.json:
{
"mcpServers": {
"bing-ads": {
"type": "http",
"url": "http://localhost:3002"
}
}
}
Claude Desktop: Add to `~/Library/Applic