AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
https://mcp.adcritter.com/mcp/devAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"com-adcritter-mcp-dev": {
"url": "https://mcp.adcritter.com/mcp/dev"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
AdCritter for Builders is an MCP server for AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.adcritter.com/mcp/dev.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.adcritter.com/mcp/dev.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.adcritter.com/mcp/dev.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.adcritter.com/mcp/dev.
AdCritter for Builders uses HTTP transport. Endpoint: https://mcp.adcritter.com/mcp/dev.
AdCritter for Builders inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
AdCritter for Builders does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.