Developer API

Connection methods

The server answers initialize, notifications/initialized, tools/list and tools/call over HTTPS POST (JSON-RPC 2.0). Notifications return an empty 202; the same tools are always callable as a plain API.

Setup

1. 1

   Create a token

   Create a project token in Developer settings and copy the one-time mad_ value. Scopes and optional expiry are applied on every call.
2. 2

   List the tools

   Call tools/list (no token needed) to confirm the endpoint and see the six available tools.

   API · Setup

   curl -X POST https://<your-site>/api/developer/mcp \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

3. 3

   Call a tool

   Send tools/call with an Authorization: Bearer header. Check the X-RateLimit-* response headers to track your window.

   API · Setup

   curl -X POST https://<your-site>/api/developer/mcp \
     -H "Authorization: Bearer mad_..." \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"ads.search","arguments":{"page":1,"pageSize":20}}}'

Try it

With the server connected, a quick smoke check:

curl -X POST https://<your-site>/api/developer/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Available tools

Common errors

Failures come back as HTTP 400 with a JSON-RPC error object (code + message), not as HTTP 401/403/429.

FAQ

Related integrations