Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Microsoft Ads MCP Server How did my Bing campaigns perform last week?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Connect Microsoft Ads (Bing Ads) to Claude, ChatGPT, Cursor, Codex or any AI app that supports MCP. AdKit hosts the server, so you only add an address to your AI app.
MCP address: https://mcp.adkit.so/microsoft-ads
Website: Microsoft Ads MCP by AdKit
Beta: Your AI writes Microsoft Advertising API requests and AdKit sends them. It can do what the API allows, with more steps than on Meta or Google. Turn on Advanced Platform Access in your AdKit project (Agent Permissions) first.
Every change is saved as a draft first, so your AI can't spend money on its own. Nothing goes live on Microsoft Ads until you approve it.
Connect your Microsoft Advertising accounts
Read campaigns and reports through the Microsoft Advertising API
Save campaign changes as drafts, then publish them after you approve
Related MCP server: Google Ads MCP Server
"How did my Bing campaigns perform last week?"
"Lower the budget of the ‘Brand’ campaign to $20 a day. Save it as a draft."
You need an AdKit account. On first use, you sign in to AdKit and connect your Microsoft Ads account.
There are two ways to connect:
All platforms: the main AdKit connector. One connection for Google, Meta, TikTok, LinkedIn, Microsoft, Reddit, X and Pinterest. Pick this if you run ads on more than Microsoft Ads.
Microsoft Ads only: the address above. Your AI only sees the Microsoft Ads tools.
All platforms: install AdKit from the Claude directory, in one click.
Microsoft Ads only: Settings → Connectors → Add custom connector → paste https://mcp.adkit.so/microsoft-ads.
All platforms: add the AdKit app, in one click.
Microsoft Ads only: Settings → Connectors → Add custom connector → paste https://mcp.adkit.so/microsoft-ads.
As a plugin:
/plugin marketplace add adkit/microsoft-ads-mcp
/plugin install microsoft-ads@adkit-microsoft-adsOr as an MCP server only:
claude mcp add --transport http adkit-microsoft-ads https://mcp.adkit.so/microsoft-adsgemini extensions install https://github.com/adkit/microsoft-ads-mcpAdd to ~/.cursor/mcp.json:
{
"mcpServers": {
"adkit-microsoft-ads": {
"url": "https://mcp.adkit.so/microsoft-ads"
}
}
}Add to ~/.codex/config.toml:
[mcp_servers.adkit-microsoft-ads]
url = "https://mcp.adkit.so/microsoft-ads"In Claude Code, Gemini CLI, Cursor and Codex, use https://mcp.adkit.so instead to connect all platforms.
What | Tools |
Ad accounts |
|
Direct API requests |
|
Every AdKit connector also has these tools:
Tool | What it does |
| List your AdKit projects and pick one |
| Show the connected ad accounts |
| Get the link to connect an ad account |
| List saved drafts, or read one |
| Edit a draft before it goes live |
| Delete a draft |
| Publish drafts after you approve them |
| Look up fields, limits and examples |
| Report a bug or a missing feature |
A hosted MCP server from AdKit. It lets Claude, ChatGPT, Cursor, Codex and other AI apps work on your Microsoft Ads account: Microsoft Advertising (Bing Ads) reports and campaign changes through its API, in beta.
It is included in every AdKit plan. Plans start at $29 a month, with a 7-day free trial. See pricing.
No. Every create, edit or pause is saved as a draft. It goes live only after you approve it, on AdKit's Draft Approval page or by telling your AI to publish it.
No. You sign in to AdKit in your browser and connect your Microsoft Ads account there. You also need to turn on Advanced Platform Access in your AdKit project (Agent Permissions), because this beta sends requests through the platform API.
Yes. Connect several accounts and keep each client in its own AdKit project. How many projects you get depends on your plan.
Claude, ChatGPT, Claude Code, Gemini CLI, Cursor, Codex and any app that supports remote MCP servers with OAuth sign-in.
Help: adkit.so/support or contact@adkit.so
docs-server/ is a small local MCP server that answers questions about AdKit from this README: setup per AI app, hosted tools, ad platforms, example prompts and the FAQ. It needs no login and does not manage ads; for that, connect the hosted server above. Run it with npm start or the Dockerfile.
MIT
Get example prompts that work with the hosted Microsoft Ads MCP server by AdKit, such as reporting, optimizing and launching campaigns. Use this when the user asks what to try first or what to ask the agent. Returns a Markdown list.
Inputs: no named parameters.
Get the answers to common questions about the hosted Microsoft Ads MCP server by AdKit: price, safety and approvals, API keys, several ad accounts and supported AI apps. Use this before answering such a question from memory. Returns Markdown, one heading per question.
Inputs: no named parameters.
Get the step-by-step instructions to connect one AI app to the hosted Microsoft Ads MCP server by AdKit at https://mcp.adkit.so/microsoft-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.
Inputs: app (required).
List the ad platforms AdKit supports (Google, Meta, TikTok, LinkedIn, Microsoft, Reddit, X, Pinterest) and the link to each platform's own MCP server and setup page. Use this when the user asks which ad platforms are supported or wants a server for one platform only. Returns Markdown.
Inputs: no named parameters.
List the tools of the hosted Microsoft Ads MCP server by AdKit (https://mcp.adkit.so/microsoft-ads), with one line on what each tool does. Use this to explain what an agent can do with ad accounts after connecting, such as creating campaigns, pulling performance or uploading media. Returns a Markdown table. It does not call those tools; they only run on the hosted server.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose: setup instructions, hosted tool inventory, platform directory, example prompts, and FAQ. The descriptions even include explicit cross-references (e.g., get_setup_guide says to use list_hosted_tools for capability info), which eliminates the main potential confusion between onboarding and capability questions.
All five tools follow a consistent snake_case verb_noun pattern (get_setup_guide, list_hosted_tools, list_ad_platforms, get_example_prompts, get_faq). The get_/list_ prefix split maps sensibly to single-item retrieval vs. collection listing.
Five tools is well-scoped for a documentation/onboarding front-end; each covers a distinct question type (install, capabilities, platforms, prompts, FAQ) with no filler. Nothing feels missing or redundant at this count.
The onboarding surface is essentially complete: setup, capability discovery, cross-platform pointers, starter prompts, and FAQ cover the full user journey for connecting to the hosted server. The only minor gap is the absence of any tool to verify a connection or account status, which would be a natural next step after setup.
Connect authorized ad accounts to AI assistants for audits, reporting, and approval-gated changes.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Manage Google, Microsoft, ChatGPT and Meta Ads safely: previewed, logged, revertible changes.
Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.
