MCP for Builders

The MCP for Builders server exposes AdCritter's build-time surface to coding agents. Connect it like any other MCP server.

Endpoint

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

Tool surface (10 tools, 5 tiers)

Reference - orient the agent and lock in the API contract.

  • get_platform_overview - entity hierarchy, happy path, and navigation across the other tools.
  • get_usage_guide(entity) - conceptual model and workflow for advertiser, campaign, ad, geo, audience, settings, report, plan, or authentication.
  • get_api_reference(entity, operation?) - REST contract for an entity; operation summary or full per-operation spec.

Design - screen experiences and API bindings, format-agnostic.

  • get_design_guide(entity, guidance?) - rigidity dial: full (default), patterns, or facts.

Starter - feature-by-feature build instructions with API snippets embedded.

  • build_app - catalog of feature guides and their keys.
  • guidance(key) - detailed instructions for a feature area, including every endpoint and response shape.

Operations - a three-tool meta-pattern covering every runtime action across advertiser, campaign, ad, media_asset, blueprint, plan, report, segment, and targeting.

  • adcritter_operation_entities - catalog of operational entities.
  • adcritter_available_operations(entity) - actions and JSON input schemas for a given entity.
  • adcritter_operation(entity, action, body?) - execute an action. Body is a JSON object matching the schema.

Health

  • health - server status and version.

Auth

OAuth2 handled by the MCP client. No env vars, no config.