Claude Code 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 and copy the one-time mad_ value.
2. 2

   Register the server

   Register the server with claude mcp add, or add it to a project .mcp.json so it is shared with your team.

   Claude Code · Setup

   claude mcp add meta-ads \
     --transport http https://<your-site>/api/developer/mcp \
     --header "Authorization: Bearer mad_..."
   
   # or share it with a team in a project .mcp.json
   # {
   #   "mcpServers": {
   #     "meta-ads": {
   #       "type": "http",
   #       "url": "https://<your-site>/api/developer/mcp",
   #       "headers": { "Authorization": "Bearer mad_..." }
   #     }
   #   }
   # }

3. 3

   Test the connection

   Run claude mcp list to confirm the server is registered, then ask Claude to search the ad library.

Try it

With the server connected, a quick smoke check:

claude mcp list

claude -p "search the ad library for running ads"

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