n8n integration

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 with the scopes your workflow needs, and copy the one-time mad_ value.
2. 2

   Add an HTTP Request node

   Add an HTTP Request node that POSTs to /api/developer/mcp with the JSON-RPC body and an Authorization: Bearer header. Start with tools/list to confirm the token works.

   n8n · Setup

   POST /api/developer/mcp
   Content-Type: application/json
   Authorization: Bearer mad_...
   
   {
     "jsonrpc": "2.0",
     "id": 1,
     "method": "tools/list"
   }

3. 3

   Call a tool

   Send a tools/call request for ads.search, monitors.list or jobs.get and use the returned JSON in the rest of the workflow.

   n8n · Setup

   {
     "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 "Authorization: Bearer mad_..." \
  -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