Bullpen

Bullpen MCP server

Bullpen is an AI sales team that works the phone. A crew of AI callers, each with its own number and voice, gets through phone trees, hold queues and AI receptionists to a real person, then drops your rep into the live call. Every call writes to Salesforce. Herman, the manager agent, runs the whole bullpen in plain language and asks before anything leaves the building.

This repository documents Bullpen's remote MCP server. There is nothing to install or host: the server runs at

https://bullpen.sale/mcp

• Transport: Streamable HTTP (stateless, JSON responses)
• Auth: OAuth 2.1 with PKCE and dynamic client registration, or a workspace API key
• Registry: sale.bullpen/bullpen in the official MCP Registry
• Site: bullpen.sale · Docs: bullpen.sale/docs · For LLMs: bullpen.sale/llms.txt

Connect

Claude (claude.ai, desktop, mobile) Settings → Connectors → Add custom connector → https://bullpen.sale/mcp. The first tool that needs your workspace sends you to bullpen.sale to sign in and click Allow.

Claude Code

claude mcp add --transport http bullpen https://bullpen.sale/mcp

Cursor, VS Code, and other MCP clients

{
  "mcpServers": {
    "bullpen": { "url": "https://bullpen.sale/mcp" }
  }
}

With an API key instead of OAuth (scripts, servers, headless agents): make a key at bullpen.sale/app/settings/api and send it as a header:

Authorization: Bearer bp_live_...

Tools

Every tool carries a title and readOnlyHint / destructiveHint / openWorldHint annotations.

Agents can hire a bullpen

An agent with a wallet can sign its principal up with no checkout page:

POST https://bullpen.sale/pay/signup?amount=25
Content-Type: application/json

{"owner_email": "ops@yourco.com", "company": "Your Co", "agent_name": "your agent"}

1. The first request returns 402 with an MPP WWW-Authenticate: Payment … challenge (cards via Stripe Shared Payment Tokens).
2. Pay and retry with Authorization: Payment ….
3. The response carries api_key, org_id and balance_cents.

Payable endpoints are described with x-payment-info in bullpen.sale/openapi.json. An agent can also attach an AP2 mandate (X-AP2-Mandate) to prove its principal authorized the spend; Bullpen checks every hop's limits and signs a receipt verifiable at /pay/ap2/jwks.

Guardrails

• A person stands behind outbound. Research, Herman, the brain, company search and campaigns work right away. Calls and texts unlock only after a workspace admin accepts the Outbound Compliance Agreement and adds a phone number.
• Herman asks first. Anything that reaches the outside world comes back as a pending action; nothing goes out until it's confirmed.
• Calling rules: company lines only unless the person gave written consent, calling hours in the callee's time zone, opt-outs honored, and the crew says it's an AI when asked.
• Permissions: a token acts as the member who approved it, in that workspace, with that member's role. It can't buy numbers, change billing, connect accounts or invite people. Revoke it any time in Settings → API keys.

Pricing

Usage-based, prepaid credits: $0.30 per crew minute, $5 per human reached, $0.03 per text, $3/month per number. New workspaces start with $10. Spending tools return a 402 error at zero. Full table: bullpen.sale/pricing.

Other ways in

• A2A: Herman is an A2A agent. Card at /.well-known/agent-card.json, JSON-RPC at https://bullpen.sale/a2a.
• REST API + CLI: one POST endpoint, every action documented at bullpen.sale/docs. curl -fsSL https://bullpen.sale/install.sh | sh

Discovery documents

Support

office@roseglass.dev · bullpen.sale · Privacy · Terms

Bullpen is built by RoseGlass Corp.