Agent setup

Bring whatever agent you already use.

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.

  1. Claude → Customize → Connectors → Add custom connector. On a Team or Enterprise plan, an owner adds it first under Organization settings → Connectors → Add → Custom.
  2. 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.
  3. 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.

Claude Code

one command

One command in the terminal; covers the CLI, the desktop app and the IDE extensions.

claude mcp add --transport http bidtune https://mcp.bidtune.com/mcp \
  --header "Authorization: Bearer bt_mcp_..."

ChatGPT

a custom connector - no file

ChatGPT's custom connectors authenticate with OAuth: nothing to paste but the endpoint - you sign in to bidtune and approve what the connection reads.

  1. ChatGPT → Settings → Apps & Connectors → Advanced settings → enable Developer mode.
  2. Create a connector, name it bidtune, paste https://mcp.bidtune.com/mcp, and choose OAuth - ChatGPT discovers bidtune's authorization server and registers itself.
  3. 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.

ChatGPT Dots

inherits workspace connectors

OpenAI's always-on workspace agents inherit the workspace's ChatGPT connectors: connect bidtune once and the Dots can read it on their own schedule.

  1. Add bidtune (https://mcp.bidtune.com/mcp) as a ChatGPT custom connector in the workspace - the ChatGPT card is the whole setup.
  2. Approve it for the site the Dot works on; the Dot inherits the connector with exactly that grant.

Cursor

.cursor/mcp.json

A few lines in .cursor/mcp.json - project-local, or ~/.cursor/mcp.json for every project.

// .cursor/mcp.json
{
  "mcpServers": {
    "bidtune": {
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

VS Code

.vscode/mcp.json

Copilot agent mode reads .vscode/mcp.json; an inputs block can prompt for the token instead of storing it.

// .vscode/mcp.json
{
  "servers": {
    "bidtune": {
      "type": "http",
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

Windsurf

mcp_config.json

Windsurf - now part of Devin - configures remote servers in mcp_config.json.

// mcp_config.json
{
  "mcpServers": {
    "bidtune": {
      "transport": "http",
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

Older Windsurf builds use "serverUrl" instead of "url", in ~/.codeium/windsurf/mcp_config.json.

Zed

settings.json

Zed takes remote servers in settings.json under context_servers.

// Zed settings.json
{
  "context_servers": {
    "bidtune": {
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

Cline

cline_mcp_settings.json

Cline's MCP Servers panel opens cline_mcp_settings.json.

// cline_mcp_settings.json
{
  "mcpServers": {
    "bidtune": {
      "type": "streamableHttp",
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

Keep "type": "streamableHttp" - without it Cline falls back to legacy SSE.

Continue

config.yaml

Continue reads mcpServers from ~/.continue/config.yaml; MCP tools run in Agent mode.

# ~/.continue/config.yaml
mcpServers:
  - name: bidtune
    type: streamable-http
    url: https://mcp.bidtune.com/mcp
    requestOptions:
      headers:
        Authorization: Bearer bt_mcp_...

Codex CLI

~/.codex/config.toml

OpenAI's Codex CLI takes remote servers in config.toml; the token can live in the file or in an env var.

# ~/.codex/config.toml
[mcp_servers.bidtune]
url = "https://mcp.bidtune.com/mcp"
http_headers = { "Authorization" = "Bearer bt_mcp_..." }

To keep the token out of the file, use bearer_token_env_var = "BIDTUNE_MCP_TOKEN" instead of http_headers.

Gemini CLI

one command

One command; Gemini CLI writes it to settings.json.

gemini mcp add --transport http \
  --header "Authorization: Bearer bt_mcp_..." \
  bidtune https://mcp.bidtune.com/mcp

Editing settings.json by hand? The streamable-HTTP key is "httpUrl" - "url" alone means SSE.

Goose

~/.config/goose/config.yaml

Block's Goose adds bidtune as a remote extension - through `goose configure` or config.yaml.

# ~/.config/goose/config.yaml
extensions:
  bidtune:
    enabled: true
    name: bidtune
    type: streamable_http
    uri: https://mcp.bidtune.com/mcp
    headers:
      Authorization: "Bearer bt_mcp_..."

The key is "uri", not "url" - with the wrong key Goose skips the extension silently.

Hermes

~/.hermes/config.yaml

Nous Research's Hermes Agent reads mcp_servers from ~/.hermes/config.yaml.

# ~/.hermes/config.yaml
mcp_servers:
  bidtune:
    url: "https://mcp.bidtune.com/mcp"
    headers:
      Authorization: "Bearer bt_mcp_..."

Verify with: hermes mcp test bidtune. After config changes, /reload-mcp picks them up without a restart.

Warp

the MCP servers page

Warp takes pasted JSON under Settings → AI → MCP servers.

// Warp → Settings → AI → MCP servers → + Add
{
  "mcpServers": {
    "bidtune": {
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

Custom headers need Warp v0.2025.12.10 or newer - older builds drop them.

JetBrains

the MCP dialog

AI Assistant takes pasted JSON under Settings → Tools → AI Assistant → MCP.

// Settings → Tools → AI Assistant → MCP → + Add
{
  "mcpServers": {
    "bidtune": {
      "url": "https://mcp.bidtune.com/mcp",
      "headers": {
        "Authorization": "Bearer bt_mcp_..."
      }
    }
  }
}

JetBrains' own docs show only the url; the headers block is vendor-reported. If the server shows red, relay through mcp-remote.

LibreChat

librechat.yaml

Self-hosted LibreChat reads mcpServers from librechat.yaml; restart after editing.

# librechat.yaml
mcpServers:
  bidtune:
    type: streamable-http
    url: https://mcp.bidtune.com/mcp
    headers:
      Authorization: "Bearer bt_mcp_..."

headers also takes ${ENV_VAR} placeholders if you'd rather not store the token in the file.

OpenHands

the MCP settings dialog

OpenHands adds bidtune under Customize → MCP Servers, with bearer auth built into the form.

  1. OpenHands → Customize → MCP Servers → Add custom server.
  2. 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.
  3. Save; the server joins the agent's tools on the next run.

OpenClaw

~/.openclaw/openclaw.json

OpenClaw (the agent once known as Clawdbot) configures remote servers under mcp.servers.

// ~/.openclaw/openclaw.json
{
  mcp: {
    servers: {
      bidtune: {
        url: "https://mcp.bidtune.com/mcp",
        transport: "streamable-http",
        headers: { "Authorization": "Bearer bt_mcp_..." },
        enabled: true
      }
    }
  }
}

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

Grok CLI

one command

xAI's Grok CLI adds bidtune with one command; the API's remote-MCP tool takes the same token.

grok mcp add --transport http bidtune https://mcp.bidtune.com/mcp \
  --header "Authorization: Bearer bt_mcp_..."

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.

grok.com & the Grok app

a connector - no file

Grok's consumer connectors authenticate with OAuth: paste the endpoint, sign in to bidtune, approve what the connection reads.

  1. grok.com (or the Grok app) → Settings → Connectors → Add connector, and paste https://mcp.bidtune.com/mcp.
  2. Grok registers itself with bidtune and opens the approval page; sign in and pick the site the connection covers.

curl

any terminal

No agent at all: the endpoint is plain JSON-RPC over HTTP, so anything that can POST can query it.

curl -X POST https://mcp.bidtune.com/mcp \
  -H "Authorization: Bearer bt_mcp_..." \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Everything else

Something we missed?

It probably already works.

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.

checked against each client's official docs · November 2026 · what your agent can do

Put your setup on trial. If we can't prove a lift, you owe nothing.

14 days free after activation. No card. One script URL to start; restore it to stop. Sign in with Google or email and add your site.

Google or email · first test starts once the holdback has traffic