AdButler

What AdButler MCP server does

The AdButler MCP server gives an MCP-compatible assistant access to the AdButler v2 API. Its tool set covers advertisers, campaigns, ad items, creatives, placements, zones, publishing resources, targeting, reporting, contracts, drafts, product catalogs, VAST video advertising, and programmatic or RTB configuration.

The API surface contains more than 600 tools. An assistant can use them to perform multi-step tasks such as creating a campaign, assigning it to zones, configuring targeting, preparing a VAST placement, or examining performance data. The server also provides nine workflow prompts for campaign launches, retail media, reporting, VAST video, programmatic deals, targeting, contracts, channels, and draft-based campaign setup.

How it works

The AdButler MCP server translates an assistant's request into the required sequence of AdButler API calls and returns the resulting data. Specific tools cover common resources and actions. Three fallback tools extend coverage when a particular endpoint or field is not represented by a dedicated tool:

• search_adbutler_api searches the AdButler OpenAPI specification.
• describe_adbutler_api returns an endpoint's parameters, request body, and response schema.
• call_adbutler_api invokes an endpoint by HTTP method and path using the current session's authentication.

The hosted service supports Streamable HTTP at /mcp and legacy SSE at /sse. A local npm installation communicates over stdio.

Setup and configuration

For the hosted option, connect an MCP client to https://mcp.adbutler.com/mcp, preferably using the Streamable HTTP endpoint. Older clients can use the /sse URL. Supply an AdButler API key in an Authorization: Bearer ... header; the hosted service also accepts the key as an api_key query parameter for clients that cannot send custom headers.

The local option runs with npx -y @adbutler/mcp-server. Set ADBUTLER_API_KEY in the client's MCP environment configuration. The key is obtained from AdButler Dashboard → Settings → API Keys and is the same credential used by the AdButler v2 REST API.

An unauthenticated hosted session can guide new users through trial account creation and email verification. Existing users can configure a key through setup tools, but a key entered in chat on the hosted service lasts only for that session. Connection-level configuration persists across sessions; local configuration can also retain the key between sessions.

Tools and capabilities

The AdButler MCP server includes tools for display advertising, VAST 2/3/4 video, zones and publishing, targeting, reporting, programmatic or RTB resources, and related account objects. Reporting tools include display and VAST reports, event logs, custom report configurations, and scheduled reports. Targeting tools cover geographic, platform, data-key, data-list, and postal-code targets.

Workflow prompts are invoked as MCP prompts, including names such as launch-campaign, retail-media-setup, reporting, vast-video, programmatic, targeting, contracts, channels, and drafts.

Limitations and notes

The hosted service's in-chat API-key setup is session-scoped and does not persist the credential to disk. Reconnecting or starting a new client session may require authentication again unless the key is supplied in the connection configuration. Clients that cannot add a custom authorization header can use the hosted URL query-parameter form where supported.

The available operations and returned data depend on the AdButler account and the permissions associated with its API key. The server is an interface to the AdButler v2 API; it does not replace that account or API access.