MCP server

The Sponsored Code MCP server gives Claude (or any Model Context Protocol client) direct tools to read network activity and manage your campaigns, right inside the chat. Ask things like “how are my ads doing?” or “launch a campaign for X”.

Install

Runs over stdio via npx. No global install, no keys, no config. Pick your client:

Claude CodeClaude DesktopCursorCodex

One line. No keys, no config:

terminal

claude mcp add sponsored-code -- npx -y sponsored-code mcp

Requires Claude Code CLI.

Sign in

Public tools work right away. The first time a tool needs your account (e.g. create_campaign), your browser opens to connect your wallet and sign once, exactly like the dashboard. You can also do it ahead of time:

scode login

The session is stored encrypted on your machine. No private key is ever typed into your terminal or your MCP config.

Tools

• network_stats: impressions, wallets earning, USDC settled, live campaigns.
• market_overview: the live bid market (top bid + active campaigns).
• recent_impressions: the latest impressions from the public ledger.
• campaign_stats · sign-in: your team’s impressions, spend, clicks, geography.
• list_campaigns · sign-in: your campaigns and their status.
• create_campaign · sign-in: launch a campaign into the live auction.

Automated · power users only

For headless or CI environments where no browser is available, you can sign in non-interactively with a brand wallet private key in SCODE_WALLET_KEY. It signs locally and is never sent, but it’s a raw private key, so treat it like any secret. Most people should use the browser sign-in above.

claude mcp add sponsored-code \
  --env SCODE_WALLET_KEY=0xYourBrandKey \
  -- npx -y sponsored-code mcp

{
  "mcpServers": {
    "sponsored-code": {
      "command": "npx",
      "args": ["-y", "sponsored-code", "mcp"],
      "env": { "SCODE_WALLET_KEY": "0xYourBrandKey" }
    }
  }
}

Next steps