Connect Claude Code
Add the MCP server to Claude Code or Codex over OAuth 2.1, or install the plugin.
Claude Code and Codex connect over OAuth 2.1 — there is no token to mint and no header to configure. Add the server, and the client discovers the authorization server itself and sends you to a browser to approve.
Add the server
claude mcp add --transport http bidandscale \
https://your-app-origin/api/mcpThen run /mcp and authorize bidandscale in the browser on first use.
Or install the plugin
The plugin bundles the golden-path playbooks and slash commands (/bidandscale:setup, :audit, :optimize,
:report, :approvals) alongside the server, and authorizes exactly the same way:
claude --plugin-url https://your-app-origin/api/mcp/plugin.zipPoint Codex at it
Add an HTTP MCP server to ~/.codex/config.toml:
[mcp_servers.bidandscale]
type = "http"
url = "https://your-app-origin/api/mcp"Codex prompts for OAuth authorization in the browser on first use.
The tools appear with the gads_ prefix. A connected session reaches the whole workspace, so call
gads_list_ad_accounts first and pass a projectId to account-scoped tools — see
Authorization.
Verify the connection
List my ad accounts, then give me the account overview for the first one.If nothing's connected yet, start with Set up over MCP.
Replace your-app-origin with your deployment's origin. It must be the app's real public origin — a localhost
origin can't complete the OAuth round-trip.