AGENT CONNECT

Your AI can ask the Doctor.

Connect your AI to your BSD account when you say so. Your saved slips and reports show up in the chats you already use.

Open agent setup

PUT THE DOCTOR IN YOUR AI

Your AI. A smarter bet.

Authorize your AI to read your saved BSD research and ask sharper follow-ups. Agent Connect needs Pro or Elite. Steps for Claude, ChatGPT, Claude Code and Codex are below.

Explore agent setup

Connections require your authorization. Review and revoke access in your workspace.

Claude
ChatGPT
OpenClaw
Meta Muse
Grok Bot
Hermes

Other clients depend on their own MCP support. Logos identify products, not partnerships or verified BSD connections.

CONNECT IN MINUTES

One address. Your Claude or ChatGPT.

Paste the BSD server address into your client, sign in to BSD, and approve only the permissions you want.

BSD MCP SERVER ADDRESS
https://api.betslipdoctor.ai/api/mcp

Claude

Web · desktop
  1. Add a custom connector

    In Claude open Customize → Connectors → + Add → Add custom connector. Name it BetSlip Doctor and paste the server address.

  2. Pick Register automatically

    Keep Sign in now. Under OAuth client choose Register automatically, then Add. BSD does not support Claude’s published identity yet.

  3. Sign in and approve

    Sign in to BSD, review the permissions, and choose Connect.

  4. Switch it on in a chat

    In a conversation open + → Connectors and toggle BetSlip Doctor. Try: “List my saved BSD reports.”

On a Team or Enterprise plan, an Owner adds the connector under Organization settings → Connectors; members then choose Connect. Free Claude plans allow one custom connector.

ChatGPT

Web
  1. Add a custom MCP server

    Open chatgpt.com/plugins, choose + → Add custom MCP server, and name it BetSlip Doctor.

  2. Paste the server address

    Under Connection choose Public endpoint. Configure authentication, read the warning, and choose I understand and want to continue.

  3. Create and sign in

    Choose Create as a plugin, review the discovered tools, then sign in to BSD and approve the permissions.

  4. Mention it in a chat

    Start a new conversation, type @ and pick BetSlip Doctor. After BSD updates its tools, open the connection and choose Refresh.

Your ChatGPT account and workspace policies decide whether custom MCP servers are allowed. Have private-preview access? Open the BSD customer plugin instead. BSD is not a public directory listing yet.

Claude Code

Run this, then /mcp to sign in from your browser.

claude mcp add --transport http betslip-doctor https://api.betslipdoctor.ai/api/mcp

Codex

Run both, then finish sign-in in your browser.

codex mcp add betslip-doctor --url https://api.betslipdoctor.ai/api/mcp
codex mcp login betslip-doctor

Connections require your authorization. Review and revoke access in your workspace. Logos identify products, not partnerships or verified BSD connections. Steps follow each vendor’s own guide, checked October 8, 2026: Claude custom connectors · ChatGPT custom MCP servers. Every tool and permission: the BSD connection guide.

AFTER YOU CONNECT

Your saved slip. One prompt.

Copy this into your connected agent. Choose a saved slip, review a fresh sportsbook link, and ask separately if you want it sent to your BSD phone.

Use my connected BetSlip Doctor customer account. If BSD is not connected or a permission is missing, tell me to authorize it in my client; never ask me to paste credentials.

Ask which of my saved BSD slips I want to review. Use get_tracked_slips to list my owned saved slips, then show_saved_slip with the selected ticketId. Do not invent a ticket, picks, odds, stake, sportsbook or location.

After I choose the exact saved slip, use prepare_sportsbook_handoff to get a fresh link for that ticket's supported sportsbook. Ask my state if needed; leave it unknown rather than guessing. Show the saved picks, current handoff status, expiry and any individual-selection or manual fallback. If a link is expired or the slip changed, request a fresh handoff before I open it. Never switch sportsbooks silently or promise prefill.

Do not send a phone notification unless I separately ask you to send this exact slip to my BSD phone. Only then, if the connected tool supports sendToPhone, call prepare_sportsbook_handoff with sendToPhone=true for the same saved ticket and sportsbook. Report the actual phonePush result; unavailable, skipped or failed delivery is not success. Do not automatically retry a phone push. If the parameter is unavailable, give me the supported link instead and explain that phone delivery is unavailable.

I review the slip in BSD and tap to open the sportsbook myself. You cannot place wagers. Never say a bet was placed, a stake accepted or a sportsbook slip prefilled without actual sportsbook confirmation.

Phone delivery needs a supported connected tool, a registered BSD device and notification access. A delivery request does not prove the notification arrived. You make the final decision in the sportsbook; your agent cannot place wagers.

HOW CONNECTION WORKS

Permission stays in your hands.

01

Choose a supported setup

Follow the steps above for Claude or ChatGPT, or start from your BSD web workspace for every other client.

02

Authorize your account

Review the access request before the client can use BSD tools with your account.

03

Review or revoke

Check your connections and revoke access from the workspace whenever you choose.