Manage AdButler campaigns, zones, ad items, VAST, and reports from Claude, ChatGPT, and Cursor.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-adbutler-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Manage AdButler campaigns, zones, ad items, VAST, and reports from Claude, ChatGPT, and Cursor.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe 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 ai-ml / marketing
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
MCP Security Weekly
Get CVE alerts and security updates for com.adbutler/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Manage your entire AdButler account from any AI assistant — Claude, ChatGPT, Cursor, Windsurf, Cline, and any other Model Context Protocol client.
This MCP server exposes the full AdButler v2 API — 600+ tools covering advertisers, campaigns, zones, creatives, placements, VAST video ads, programmatic / RTB, reporting, targeting, drafts, contracts, product catalogs, and more — plus 9 pre-built workflow prompts that walk an AI through common tasks like launching a campaign or setting up retail media.
"Create a new campaign for Pepsi targeting users in Canada with a $5,000 lifetime budget, and assign it to my Homepage Banner zone."
"Show me the top 10 underperforming ad items in the last 7 days by CTR."
"Set up a VAST 4.2 pre-roll campaign with a 30-second skippable creative and three companion banners."
"Walk me through creating a new programmatic deal."
"Audit my ad units — which zones have no active placements?"
The AI translates these into the right sequence of AdButler API calls, runs them, and shows you the result.
You have two options. Most users want the hosted version — zero setup, just paste a URL.
Use AdButler's hosted MCP server. No install, no Node, no npm.
The hosted server speaks both modern Streamable HTTP (/mcp) and legacy SSE (/sse) transports. New clients should prefer Streamable HTTP; SSE remains for backward compatibility.
| Client | Configuration |
|---|---|
| Claude Desktop / Code | Add an MCP server with URL https://mcp.adbutler.com/mcp (or /sse for older clients) and header Authorization: Bearer YOUR_ADBUTLER_API_KEY |
| Cursor | Settings → Features → Model Context Protocol → Add server with the URL + auth header above |
| Any MCP client | Streamable HTTP: https://mcp.adbutler.com/mcp · SSE: https://mcp.adbutler.com/sse — pass your API key via Authorization: Bearer … or ?api_key=… |
Run the server locally as a Node process. Useful if you want to keep your API key out of any external service or run against a self-hosted AdButler.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"adbutler": {
"command": "npx",
"args": ["-y", "@adbutler/mcp-server"],
"env": {
"ADBUTLER_API_KEY": "your_api_key_here"
}
}
}
}
claude mcp add adbutler --env ADBUTLER_API_KEY=your_api_key_here -- npx -y @adbutler/mcp-server
Add to the client's MCP config:
{
"mcpServers": {
"adbutler": {
"command": "npx",
"args": ["-y", "@adbutler/mcp-server"],
"env": { "ADBUTLER_API_KEY": "your_api_key_here" }
}
}
}
AdButler Dashboard → Settings → API Keys → create a new key. It's the same key the AdButler v2 REST API uses.
The AdButler MCP works for both new and existing customers. What you see depends on whether you've already configured an API key.
Use one of these:
Option 1 — set the API key in your client config (recommended for hosted)
Add an Authorization: Bearer YOUR_ADBUTLER_API_KEY header on the SSE connection. Examples:
claude_desktop_config.json → add headers: { "Authorization": "Bearer YOUR_API_KEY" } next to the SSE URLAuthorization: Bearer YOUR_API_KEY