Connect n8n to AdKit

Use AdKit inside n8n to automate your Meta, Google, TikTok, and Reddit ad workflows through the MCP Client Tool.

Connect the MCP Client Tool

1. Create an API key under Devices & Keys. It is shown once, so copy it immediately.
2. Add an MCP Client Tool node to your workflow.
3. Configure it with these values:

   Endpoint: https://mcp.adkit.so
   Server transport: HTTP Streamable
   Authentication: Bearer Auth
   Bearer token: adk_your_key
   

4. Connect the MCP Client Tool to your AI Agent node and save the workflow.

Keep the key in the n8n credential, not in a workflow prompt or chat message.

Check it worked

Run the workflow with this test message:

Use the AdKit checkin tool with agentId: "n8n", then list my connected ad accounts.
Tell me if AdKit is connected and ready. If not, tell me what failed.

What you can do

Once connected, n8n can pull your live campaigns, draft budget and targeting changes, and research competitors as part of a workflow. Nothing goes live on its own: every change is saved as a draft for you to review and publish.

Troubleshooting

The node connects but calls fail with an auth error. The Bearer token must be the full key starting with adk_, nothing else around it. If the key was revoked or lost, create a new one under Devices & Keys: it is shown once.

The tool lists zero AdKit tools. Check the endpoint is exactly https://mcp.adkit.so and the transport is HTTP Streamable, then re-save the credential and run the workflow again.

Rotate or revoke a key. Revoke the old key under Devices & Keys, create a new one, and update the n8n credential. API keys don't expire on their own.

Need a hand? Reach out and we'll help.