Production-grade MCP server for Microsoft Advertising (Bing Ads) API that enables management of Bing/Microsoft Ads accounts with full campaign, ad group, keyword, and performance analysis capabilities.
From the registry: MCP server for Microsoft Advertising (Bing Ads) — campaigns, keywords, and reports
$ npm install mcp-bing-adshttps://www.npmjs.com/package/mcp-bing-adsPlease install the `bing-ads` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Microsoft Advertising OAuth + developer token** — Create an Azure AD app registration, grant Microsoft Advertising API permissions, and obtain a Bing Ads developer token. (https://portal.azure.com/)
- **npm install mcp-bing-ads and npm start** — Clone/install the server locally — it runs its own HTTP listener on port 3002. Run: `npm install mcp-bing-ads` (https://www.npmjs.com/package/mcp-bing-ads)
Canonical MCP server config (HTTP transport):
- url: `http://localhost:3002`
Note: Server runs as a local HTTP listener after `npm start`. OAuth creds (BING_ADS_DEVELOPER_TOKEN, BING_ADS_CLIENT_ID, BING_ADS_REFRESH_TOKEN, BING_ADS_CLIENT_SECRET) are read from env or config.json at server startup.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.BING_ADS_DEVELOPER_TOKENrequiredYour developer token for Bing Ads API access.BING_ADS_CLIENT_IDrequiredYour Azure client ID for OAuth authentication.BING_ADS_REFRESH_TOKENrequiredYour refresh token for OAuth authentication.BING_ADS_CLIENT_SECRETYour client secret for OAuth authentication (required if using a confidential app).MCP server for Tiny ERP — products, stock, warehouses, price lists, orders, invoices, AP/AR