mcpbeat

AdCritter for Builders MCP Server

com.adcritter/mcp-dev
answering

AdCritter for Builders is answering right now. Last checked 12 min ago. It exposes 7 tools.

AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
658 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp-dev --transport http https://mcp.adcritter.com/mcp/dev
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-dev": {
      "url": "https://mcp.adcritter.com/mcp/dev"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-dev]
url = "https://mcp.adcritter.com/mcp/dev"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-dev": {
      "url": "https://mcp.adcritter.com/mcp/dev"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-dev": {
      "url": "https://mcp.adcritter.com/mcp/dev"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

adcritter
adcritter_build_app
Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
adcritter_get_api_reference
Returns the REST API contract for an AdCritter entity. Without an action parameter, returns a summary with available action names - use this to discover what you can do. With an action parameter (e.g., 'create', 'list', 'get'), returns the full details for that action: route, HTTP method, request schema, response schema, error codes, and constraints. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, canva, domain, facebook, geo, googleads, media-asset, me, plan, report, segment, settings, targeting.
adcritter_get_design_guide
Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.
adcritter_get_platform_overview
Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.
adcritter_get_usage_guide
Returns the conceptual model and workflow guidance for an AdCritter entity - what it is, how it relates to other entities, and the intended workflow for using it. Includes exhaustive workflow sequencing and prescriptive rules so generated apps call the API correctly. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, domain, geo, media-asset, me, plan, report, segment, settings, targeting.
adcritter_guidance
Returns detailed building instructions for a specific feature area of an AdCritter application. Each guide describes what to build, how users should experience it, and includes all API endpoints with request/response shapes so you never have to guess the API contract. Call adcritter_build_app first to see available feature guides and their keys.
adcritter_health
Returns server health status and version information for the AdCritter MCP server

Endpoints

URLTransportStateLatencyChecked
https://mcp.adcritter.com/mcp/dev streamable-http answering 654 ms 12 min ago

AdCritter for Builders — questions

Answers built from our own checks of this server.

What can AdCritter for Builders do?
It exposes 7 tools, read directly from the server on our last check. Among them: adcritter_build_app, adcritter_get_api_reference, adcritter_get_design_guide, adcritter_get_platform_overview, adcritter_get_usage_guide, adcritter_guidance and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AdCritter for Builders working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 658 ms. The bar chart above shows every period we have measured.
How do I connect AdCritter for Builders?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AdCritter for Builders need an API key?
No. AdCritter for Builders completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AdCritter for Builders?
It answers our handshake in 658 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.