BotPhone MCP

How it works

1. You get a phone number. Pick an area code and BotPhone sets up a US number for your receptionist.
2. You tell it about your business. Name, hours, services, common questions, and what counts as urgent.
3. Callers reach the AI. It says it's an AI assistant, answers from what you told it, and takes a message with the caller's name, number, and reason.
4. You hear about it. A summary is emailed to you, and you can ask your connected assistant about any call.

The receptionist only states facts you gave it. If it doesn't know something, it says so and offers to take a message.

Get started

1. Open the sign-in page and continue with Google, or create an account with email and password.
2. Tell us your business name, your website if you have one, and anything callers should know. We read your website so your receptionist knows your services, prices, and hours.
3. Choose an area code and pick your number.
4. Choose how to pay: the monthly plan, or pay as you go (setup costs $4, see pricing). Eligible launch-offer accounts have the setup fee and first month waived.
5. Call your new number to hear your receptionist. Call summaries go to the email you signed up with; change that under Call summaries on the dashboard.

Everything else lives on the dashboard: tap Business details to change what your receptionist knows. Answer a few questions, or choose Write it myself to write its instructions in your own words. Every change is kept under Past versions.

Forward your business calls

Most owners keep their current business number and forward it to the BotPhone number when they can't answer. On the dashboard, tap Your business number and pick your phone company. It shows the one code to dial, filled in with your number, plus steps for other carriers and office phone systems.

Forwarding is set up with your own phone carrier, and any carrier charges are yours. After setting it up, call your business number from another phone and let it ring to test it.

Book meetings with Calendly

Your receptionist can put callers straight onto your Calendly during the call. It asks a question or two to pick the right meeting type, offers two or three open times, confirms the caller's name and email, and books it. Calendly sends the caller its usual confirmation and calendar invite.

1. On the dashboard, tap Booking, then Connect Calendly.
2. Sign in to Calendly if asked, and tap Allow. You come straight back to your dashboard, connected.
3. Turn on the meeting types your receptionist may book. For each one, write who it's for, like "qualified leads ready to talk pricing" or "anyone curious, group intro session". The receptionist uses these lines to choose.
4. Tap Check my next open times to confirm it can see your calendar, then call your number to try it.

Booking by API needs a paid Calendly plan. On Calendly's free plan, the receptionist offers to email callers your booking link instead. If the connection stops working, we email you and the receptionist falls back to the booking link until you tap Reconnect Calendly.

Connect your assistant

BotPhone is a remote MCP server. Any assistant that can add a remote MCP server with OAuth can connect, and you can connect more than one to the same line. They all use the same server URL. Most sign in with OAuth; Muse uses an API key instead (see Muse).

https://auth.botphone.tel/mcp

After you add it, a BotPhone sign-in opens. Sign in (or create your account), review what the assistant can do, and tap Allow. If your line isn't set up yet, you can set it up then or later.

Grok Bot

1. Ask Grok Bot in a chat: "Add a custom server as an MCP connector called BotPhone with the server URL https://auth.botphone.tel/mcp". Saying "custom server" keeps it from installing a catalog plugin instead. It shows the name and URL; check them and tap Add. Or add it yourself in the Grok Bot app under Settings, Connectors, Add custom connector.
2. Sign in to BotPhone and tap Allow.

ChatGPT and Dots

1. In ChatGPT, open Settings, Apps & Connectors, Advanced, and turn on Developer mode. Workspace admins may need to allow it.
2. Choose Create, name it BotPhone, paste the server URL, and pick OAuth.
3. Sign in to BotPhone and tap Allow. Dots reach apps through the same ChatGPT connectors, so a dot you allow to use BotPhone can check and place calls.

Codex

codex mcp add botphone --url https://auth.botphone.tel/mcp
codex mcp login botphone

Claude and Claude Code

1. In Claude, open Settings, Connectors, Add custom connector. Name it BotPhone and paste the server URL.
2. Sign in to BotPhone and tap Allow.

In Claude Code, run this, then run /mcp, choose botphone, and sign in:

claude mcp add --transport http botphone https://auth.botphone.tel/mcp

OpenClaw

Add this under mcp.servers in ~/.openclaw/openclaw.json, then run openclaw mcp login botphone. Open the link it prints, sign in to BotPhone, tap Allow, and return to the terminal:

"botphone": {
  "url": "https://auth.botphone.tel/mcp",
  "transport": "streamable-http",
  "auth": "oauth"
}

Hermes Agent

Add this under mcp_servers in ~/.hermes/config.yaml, then run hermes mcp login botphone in a fresh terminal and start a new session:

mcp_servers:
  botphone:
    url: "https://auth.botphone.tel/mcp"
    auth: oauth

Any other MCP client

Use the server URL above with OAuth 2.0 (authorization code with PKCE, dynamic client registration). Discovery is at https://auth.botphone.tel/.well-known/oauth-protected-resource.

If your client takes an API key instead, create one in the dashboard under Connect your AI assistant and send it as Authorization: Bearer <key> or X-API-Key: <key>.

Muse

Muse connects to BotPhone with an API key. There's no sign-in step, so it works the same in the Muse app on iPhone, Android, and desktop.

1. Sign in to your BotPhone dashboard (or create a free account) and tap Muse.
2. Copy the message (below, or from the dashboard) and send it in a chat with Muse. Muse shows a Connect button.
3. Back in the dashboard, tap Get my Muse key and Copy key. Copy the key last, right before you tap Connect in Muse, so it is what's on your clipboard.
4. Paste the key in Muse's secure box and tap Add. Never paste the key into the chat itself.

Add BotPhone as a custom connector. Server: https://auth.botphone.tel/mcp. It uses an API key, not sign-in. Open the secure form so I can paste my key.

Copy message Copied.

Your key gives Muse access to your line, including placing calls on your credit. If you ever paste it somewhere it shouldn't be, revoke it in the dashboard and create a new one. Revoking takes effect immediately.

Manual setup

1. In Muse, ask it to add a custom connector.
2. Server URL: https://auth.botphone.tel/mcp. Use the full URL, including /mcp.
3. Authentication: API key, sent as Authorization: Bearer <key>. BotPhone also accepts the key in an X-API-Key header.
4. Paste your key into Muse's secure credentials form.

Then try:

• "Who called my business today?"
• "Did I get any urgent messages?"
• "What did the last caller want? Read me the details."
• "Tell callers we're closed on Monday."
• "Read this website so my agent can answer questions about it."
• "Show me what my agent's instructions used to say."
• "How much credit do I have left on my phone line?"
• "Send me a link to add more credit."

Muse asks you to confirm before it changes your agent's instructions or knowledge. Muse can place calls when you ask it to, and placed calls spend your prepaid credit. It can also give you a payment link, and nothing is charged until you pay.

Tool reference

These are the tools a connected assistant can use. Each one acts only on your own line. Nothing takes a line or account ID as input, so one owner can never reach another's data.

Connecting the MCP endpoint directly

Hosted MCP endpoint (Streamable HTTP):

https://auth.botphone.tel/mcp

Sign-in uses the OAuth 2.0 authorization code flow with PKCE (S256). Discovery metadata is published at /.well-known/oauth-protected-resource. Clients that use API keys send a dashboard key as Authorization: Bearer <key> or X-API-Key: <key>.

Pricing

Two ways to pay, both in minutes: buy minutes as you go, or take the monthly plan. No contract, and you can switch any time.

Calls are billed by the second. Answering a call uses one minute per minute of talk time, so a 30-second call uses half a minute. Calls your agent places use minutes the same way.

Getting started on pay as you go costs $4: the $2 setup fee plus the first month of the number. On the monthly plan, your first $25 covers the number and 150 minutes.

For an eligible launch-offer account, getting started costs $0. After the free first month, the normal $2 monthly number fee comes out of your minutes, or you can move to the monthly plan. Unused promotional credit can be used toward that renewal.

Example months

Pay-as-you-go estimates include the $2 monthly number fee. The plan pays off once you use about 115 minutes a month. Taxes may apply.

How minutes work

• Your dashboard shows the minutes you have left. Buy minute packs by card or Link through Stripe. Your setup fee, the monthly number fee on pay as you go, and calls all come out of the same minutes.
• On the monthly plan, you get 150 plan minutes each month. Calls use plan minutes first. Plan minutes reset when the plan renews, and end with the plan if you cancel. Minutes you buy as packs never expire.
• Auto top-up is optional: pick a threshold (10, 25, or 50 minutes) and a pack, and we charge your saved card when you drop below it. If a charge fails, auto top-up turns off and we email you.
• We email you once when you drop below 15 minutes.
• If you run out of minutes, the receptionist stops answering calls until you add more. Your number stays yours.
• On pay as you go, if the $2 number fee can't be paid, you have 7 days to add minutes, with email reminders before the deadline. After that the number is released and can't be recovered.
• On the monthly plan, the plan pays for your number. If a plan payment fails, Stripe retries the card, and if the plan ends we hold your number for 30 days before releasing it.
• Cancel the plan any time from Manage billing in the dashboard. It stays active until the end of the month you paid for.

Limits and requirements

• US phone numbers, for US small businesses. The receptionist answers inbound calls, and places outbound calls only when you ask, to US and Canadian numbers of people who expect them.
• Phone calls today. WhatsApp calling isn't available yet.
• One phone line per account.
• A single call is capped at 10 minutes.
• Up to 5 email addresses for call summaries. Profile text fields hold up to 4,000 characters each.
• Not for emergencies. The receptionist can't reach 911 or emergency services, so keep another way to reach them.
• You need a BotPhone account (Google or email sign-in) and prepaid credit.

Data and privacy

What we store

• Your account and business details, and your receptionist's settings.
• For each call: the caller's number, the transcript, a summary, the reason for the call, urgency, and any message left.
• We don't record call audio. Only transcripts and summaries are kept.
• Card payments are handled by Stripe. We never see or store card numbers.

Where call details are sent

• Call summary emails go to the addresses you set and include the summary, the caller's message, call details, and the full transcript.
• If you place calls through the BotPhone API with a webhook and ask for transcripts, the transcript is also sent to the webhook URL you choose.
• If you connect Calendly, callers who book give their name and email, which go to your Calendly account, and callers who ask for your booking link get one email with it. Meetings booked during a call show in the call summary.

AI disclosure

The receptionist tells every caller at the start of the call that it's an AI assistant.

What a connected assistant can see

When you connect an assistant, it can read your call list, summaries, full transcripts, your receptionist's settings, your line status, and your balance. It can change your receptionist's settings, with your confirmation, and place calls when you ask it to. You can disconnect BotPhone at any time from your assistant's connector settings.

Who processes data

To run the service we use: Twilio (phone numbers and calls), LiveKit (real-time audio and AI inference), Deepgram (speech to text), Fish Audio (text to speech through LiveKit), Gemma (conversation and call summaries through LiveKit), OpenAI (knowledge-base search embeddings), Supabase (database and sign-in), Render (hosting), Stripe (payments), Resend (email), Google (optional sign-in), and, if you connect it, Calendly (booking meetings during calls).

How data is protected

• Your data is encrypted at rest in our database. The access Calendly grants BotPhone is also encrypted before it's stored. Disconnecting revokes it.
• Staff access to account data is limited, and admin actions and transcript views are logged.
• Call audio is never recorded.

Deleting your data

Text transcripts, summaries, and messages are kept while your BotPhone account is active. To delete your account and data, email info@botphone.tel. Deletion excludes logs, backups, and copies held by subprocessors, which are removed on their own schedules.

Read the full privacy policy and terms.

Sign-in and security

• Most assistants connect with the OAuth 2.0 authorization code flow and PKCE (S256). You approve access on a BotPhone page, and you can revoke it any time.
• Muse and other API-key clients use a key you create in the dashboard. Only a hash of each key is stored, it is shown once, and you can see when it was last used and revoke it any time.
• Every request is verified and limited to your own line.
• The receptionist tells every caller it's an AI, and it only states facts from your saved prompt and knowledge.

Troubleshooting

Support

Email info@botphone.tel. We're a small team and read everything.