MCP for Agents

The MCP for Agents server exposes AdCritter's runtime surface to automation platforms and in-product LLMs. Where the Builders MCP teaches agents how to build, this MCP lets agents actually run live AdCritter operations through a small dispatcher pattern — one call shape covers every entity, no per-route bindings. Every tool name starts with adcritter_.

Endpoint

server url
https://mcp.adcritter.com/mcp/agent

Tools vs. actions

The server exposes a tiny set of tools that dispatch the AdCritter REST API's actions (the verbs on each entity — list, get, create, update, delete, launch, etc). You don't bind a tool per route; instead the dispatcher tool takes an entity, an action, and a JSON body that matches the action's input schema.

Tool surface (5 tools)

Discovery

  • adcritter_entities — catalog of all operational entities the dispatcher supports (advertiser, campaign, ad, media-asset, blueprint, plan, report, segment, targeting, and so on), each with a short description and its relationships.
  • adcritter_entity_actions(entity) — every action available on an entity along with the full input and output schemas. Read these schemas before calling the dispatcher.

Execution

  • adcritter_action(entity, action, body?) — invoke an action. body is a JSON object matching the input schema returned by adcritter_entity_actions. The dispatcher returns the same response shape the AdCritter REST API would return for that action.

Context

  • adcritter_get_usage_guide(entity) — conceptual model and workflow for an entity: what it is, how it relates to the others, and the prescribed sequencing for using it. Mirrors the equivalent tool on the Builders MCP, surfaced here so agents can ground a multi-step automation without leaving the agents server.

Health

  • adcritter_health — server status and version.

Recommended workflow

  1. Call adcritter_entities once to see what's available.
  2. For each entity you'll touch, call adcritter_entity_actions(entity) to get the actions and input schemas. Optionally call adcritter_get_usage_guide(entity) for sequencing rules and constraints.
  3. Call adcritter_action(entity, action, body) with a body that matches the schema. The dispatcher returns the same response the AdCritter REST API would.

Auth

API key from your AdCritter account, sent in the X-Api-Key header — the typical choice for automation platforms that need a static credential. OAuth 2.1 is also supported for MCP clients that handle sign-in themselves.