adPluga

MCP

Connect an AI agent

adPluga runs an MCP (Model Context Protocol) server. An assistant connected to it can register and verify your site, add ad slots, ask advertisers for direct deals, join the Pool, upload images and create campaigns and ads, always with the permissions you give it.

1. Connect with your account

claude.ai, ChatGPT and Claude Code ask you to sign in to adPluga and choose the permissions and the mode (Test by default). There is no key to copy, and the connection is removed in Settings › AI assistants.

  • In claude.ai: Customize › Connectors › Add custom connector, with the URL https://api.adpluga.com/v1/mcp and no OAuth client of your own.
  • In ChatGPT on the web: Plugins › + › Add custom MCP server, with the same URL and OAuth authentication.

In Claude Code, add the server and type /mcp to sign in:

claude mcp add --transport http adpluga https://api.adpluga.com/v1/mcp

2. Or with a key

For clients that don't sign in with OAuth, such as Cursor, or for automation: in Settings › Keys create an integration key with the mcp:use scope plus the scopes of what the client may do, and send it in the Authorization header. Start with an ak_test_ key: in test mode nothing is charged or paid.

claude mcp add --transport http adpluga https://api.adpluga.com/v1/mcp \
  --header "Authorization: Bearer ak_test_•••"

What the agent can do

Each tool calls one adPluga API endpoint and needs that endpoint's scope on the key.

  • Monetise a site or app: create_property, verify_property, create_slot and get_slot_tag (scopes property:write, property:verify, slot:write and slot:read).
  • Direct deals: browse_marketplace finds advertisers' ads, request_handshake asks for a deal and list_deals shows the approved ones; advertisers answer with approve_handshake or reject_handshake (marketplace:read, handshake:read, handshake:write and deal:read).
  • Pool: set_pool_participation lets other advertisers' ads fill your slots for a revenue share (tenant:update; get_account reads it with tenant:read).
  • Advertise: create_campaign, upload_image, create_ad and activate_campaign (campaign:write, asset:write and ad:write).
  • Results: get_daily_stats and get_campaign_report (reports:read).
  • Questions: search_docs searches this documentation and needs no other scope.

Limits

  • The connection, or the key, acts as the person who created it: the assistant can never do more than that person, and loses a permission when they do.
  • Billing, wallet, payouts, members and key management are not reachable through the MCP server, whatever the permissions.
  • Verifying a site still needs the token published on your domain, and every ad goes through review before it serves.
  • upload_image takes PNG, JPEG, WebP or GIF up to 2 MiB.
  • Repeating a create with the same arguments returns the first result instead of creating a second one.
  • Each account can make 120 calls per minute.
  • In test mode the marketplace lists only test-mode ads, so asking for real deals needs a Live connection or key.