bidtune's MCP server hands your AI the same auction ledger our experiments run on - every bidder's response, timing, price and win, scoped to one token per site. If your agent speaks MCP over HTTP, it can connect. These do, today.
The whole setup
One endpoint. One header - or one sign-in.
Most cards below are the same two facts in that client's own syntax: this endpoint, and an Authorization: Bearer header carrying a token you mint on the dashboard's Your AI tab. ChatGPT and Grok's own apps skip the token: pick OAuth, sign in to bidtune, and approve what the connection reads. Either way it reads one site's data and can do exactly one kind of write: propose an experiment draft that an owner approves.
https://mcp.bidtune.com/mcp
Supported today
Pick your agent.
Each snippet was written against the client's current official docs, caveats included. Swap bt_mcp_... for your site's token; the dashboard shows these same snippets with the token already in place.
Claude
a custom connector - no file
claude.ai and the desktop app take the endpoint and the header in the custom-connector dialog.
Claude → Customize → Connectors → Add custom connector. On a Team or Enterprise plan, an owner adds it first under Organization settings → Connectors → Add → Custom.
Name it bidtune, paste https://mcp.bidtune.com/mcp, and choose No sign-in. Under Request headers, set Authorization to Bearer bt_mcp_.... Claude sends that value as typed.
Ask something. The connector menu lists the ready-made prompts.
Request headers are in beta and not on every account yet; without that section the token cannot be attached.
Create a connector, name it bidtune, paste https://mcp.bidtune.com/mcp, and choose OAuth - ChatGPT discovers bidtune's authorization server and registers itself.
Sign in on the bidtune page that opens and choose what the connection covers: one site, or everything your account reads.
Custom connectors need developer mode and a Plus, Pro, Business, Enterprise or Edu plan. The grant covers the site you pick on bidtune's approval page; drafts it files still wait for a human in Experiments.
Name it bidtune, paste https://mcp.bidtune.com/mcp (transport SHTTP), choose Bearer token authentication, and paste bt_mcp_... as the key. OpenHands sends it as Authorization: Bearer.
Save; the server joins the agent's tools on the next run.
Use openclaw 2026.5.12 or newer - earlier builds could forward the header on a cross-origin redirect (CVE-2026-53840). Check with: openclaw mcp doctor bidtune --probe
By hand it's [mcp_servers.bidtune] with url and headers in ~/.grok/config.toml. Over the API, pass the token as the remote-MCP tool's authorization value - bidtune accepts it with or without the Bearer prefix.
If it can POST JSON-RPC with one header, it already works - the curl card is the whole protocol - and OAuth-only connectors get the same flow ChatGPT uses. Running an agent we haven't listed? Tell us: hello@bidtune.com.