What Kaminari Ad MCP server does
Kaminari Ad MCP server gives MCP-compatible AI clients access to the Kaminari Ad ad verification platform. Its scan functions can create one-off or bulk checks, retrieve scan status and details, recheck or cancel work, and enumerate related scan records. Agents can also inspect captured evidence, including screenshots of the scan, creative, and landing page, along with creative HTML, video, and VAST XML.
The server covers more than scan retrieval. Campaign tools support campaign lookup and campaign selection, while the broader API surface includes campaign groups, runs, tags, custom rules, custom taxonomies, policy sets, alerts, webhooks, billing, invoices, alert destinations, and reference data such as geographies and emulator profiles. Account tools handle organization settings, users, roles, labels, and API keys.
How it works
The local version runs as an MCP process and forwards authenticated tool requests to Kaminari Ad using an API key. A hosted streamable HTTP endpoint is also available at https://mcp.kaminari.ad/mcp, which can be used by clients that do not have a local Node.js runtime. Hosted access accepts a Bearer API key, and interactive clients can use the documented OAuth 2.0 authorization-code flow with PKCE and dynamic client registration.
Returned evidence is made available directly through MCP. Screenshots are returned as image blocks, video and invoice PDFs as resource blocks, and HTML or VAST XML as readable text. Gateway limits cap text artifacts at 256 KiB and binary artifacts at 8 MiB.
Tool metadata includes MCP behavior annotations such as read-only, destructive, idempotent, and open-world hints. Clients can use these annotations when presenting or confirming operations that change account data or cancel work.
Setup and configuration
Install the package with an MCP client configuration that runs npx -y @kaminari-ad/mcp, then provide KAMINARI_AD_API_KEY in the client environment. Cursor and Claude Desktop use local configuration files; Claude Desktop also has a downloadable MCPB package. Claude Code can register the server with claude mcp add and receive the key from the shell environment.
Alternatively, configure the hosted URL and send the key in an Authorization: Bearer header. API keys are generated in Kaminari Ad under Settings → API Keys and are shown only once. Treat the complete value as a secret. OAuth is intended for interactive agents that need per-application consent and revocation, while API keys are the documented choice for command-line use and one-off scripts.
Tools and capabilities
The Kaminari Ad MCP server exposes tools across these supported areas:
- Account administration, organization users, roles, labels, and API keys
- Scan creation, bulk scans, status inspection, cancellation, rechecks, and evidence retrieval
- Campaign and campaign-group management, runs, and scheduling controls
- Tags, custom rules, custom taxonomies, and policy sets
- Alert status, alert statistics, destinations, and campaign overrides
- Webhook configuration, testing, delivery inspection, secret rotation, and replay
- Billing, usage, invoices, geographies, emulators, and proxy targeting
The listed scan workflow supports selecting locations and emulator profiles, waiting for completion, reading results, and reviewing scan tags. Destructive operations are annotated so compatible clients can distinguish them from read-only requests.