mcp

POST /v1/mcp/ads

The Zinn® Ads MCP endpoint — the same protocol, serving only the Zinn® Ads tools.

All mcp endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/mcp/ads \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": <string<2.0>>, "method": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

The "Zinn® Ads" listing in the Claude and ChatGPT directories (docs/925 §1b). Same JSON-RPC 2.0 protocol as /v1/mcp, but tools/list and tools/call cover only the ads_* tools (any other tool answers unknown tool), and resources/list and prompts/list are empty. Authenticated only by an OAuth access token issued for this URL (RFC 8707 resource): a token issued for /v1/mcp, or a pasted zmcp_… token, is refused with 401, and a token issued here is refused at /v1/mcp. The consent screen for this resource offers only the Zinn® Ads permissions.

Request body

NameTypeRequiredWhat it is
jsonrpcstring<2.0>Yes—
idstring | integerNoRequest id (string or number); omit for a notification.
methodstringYes—
paramsobjectNo—

Response

NameTypeRequiredWhat it is
jsonrpcstring<2.0>Yes—
idstring | integer | nullYes—
resultobjectNo—
errorobjectNo—

Errors this endpoint can return

401 · 429