Bing Ads MCP Server

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:

• 13 tools (9 read, 4 write) -- production-tested
• Campaign, ad group, and keyword management
• Keyword performance analysis with quality scores
• Search term reporting & bid automation
• Budget & bid strategy optimization
• Campaign-level budget updates
• Negative keyword management (shared + campaign-level)

Note: Microsoft also publishes an official, read-only Microsoft Advertising MCP server (open pilot). This server adds search term and Quality Score reporting, shared negative list audits, and a small set of guarded write tools.

Installation

npm install mcp-bing-ads

Configuration

Security: Never share your .mcp.json file or commit it to git -- it may contain API credentials. Add .mcp.json to your .gitignore.

1. Get OAuth credentials:

   • Go to Microsoft Azure Portal
   • Create an Azure AD app registration
   • Grant API permissions: Microsoft Advertising API
   • Scopes: https://ads.microsoft.com/msads.manage offline_access

2. Create config.json:

   cp config.example.json config.json
   

3. 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"
       }
     }
   }
   

4. 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"
   

Environment Variables

Read-only by default

Mutating tools (bing_ads_pause_keywords, bing_ads_update_campaign_budget, bing_ads_update_ad_group_cpc_bid, 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.

Usage

Use with Claude Code

The server runs locally over stdio; your MCP client starts it. Add to ~/.claude.json (or a project .mcp.json):

{
 

... [View full README on GitHub](https://github.com/mharnett/mcp-bing-ads#readme)