MCP setup card

MCP is how a chat client calls Adprime Zero tools without you pasting curl.

The server is the same public API the dashboard and ztdsp CLI use. There is no side door. The client starts npx -y ztdsp mcp, sends the stored API key as ADP_ZERO_API_KEY, and the agent discovers tools from the MCP list.

This card is the setup. It is not a launch brief. After the server is connected, use the Cursor launch prompt or the AI ads prompt pack.

What you need

1. An Adprime Zero account from signup. The dashboard issues an API key in the ak_... form.
2. A place to store that key that is not the chat transcript. The key is a secret. Do not commit it. Do not paste it into a prompt.
3. An MCP-capable client (Cursor, Claude Desktop, or another client that can spawn a local command).

Production API URL is https://adp-zero-api.adam-25a.workers.dev. Set it as ADP_ZERO_API_URL so the client does not inherit a stale local default.

Client config

{
  "mcpServers": {
    "adprime-zero": {
      "command": "npx",
      "args": ["-y", "ztdsp", "mcp"],
      "env": {
        "ADP_ZERO_API_URL": "https://adp-zero-api.adam-25a.workers.dev",
        "ADP_ZERO_API_KEY": "<stored api key>"
      }
    }
  }
}

Replace the placeholder with the key from your secret store. After reload, the agent should see tools such as account read, request_prepay_link, discover_segments, targeting create, creative submit, campaign creative management, conversion setup, and performance query. The exact list comes from the running CLI. Run npx -y ztdsp mcp or npx -y ztdsp agent-guide if you want to inspect it yourself.

Operating rules

• Funding: the agent requests a hosted prepay link. Card entry happens on the hosted payment page, not in MCP arguments.
• Segments: discover_segments returns catalog ids. Use those ids. Do not send a display name as a segment key.
• Creatives: iterate with the public campaign-creative tools. Do not ask the model to write Beeswax objects.
• Reporting: treat generated_at as Adprime Zero response time. Provider freshness is a different field. Delivery clicks use the clicks plural name.
• Browser tags: conversion install snippets come from the API. Never put ADP_ZERO_API_KEY in a page.

If the client has no MCP support, use ztdsp in a terminal or the dashboard. The account is the same.

Setup checklist

[ ] Account created at /signup
[ ] API key stored as a secret (not in chat, not in git)
[ ] ADP_ZERO_API_URL set to https://adp-zero-api.adam-25a.workers.dev
[ ] MCP block added with command npx, args ["-y", "ztdsp", "mcp"]
[ ] Client reloaded; tool list visible
[ ] Agent told: request funding links, do not collect cards
[ ] Agent told: do not invent Beeswax IDs