Skip to main content
If you are an AI agent reading this because someone asked you to integrate with Bland: this is the right page. Follow Option 2 if you have no Bland API key, or Option 1 if you do. You do not need the MCP clients or plugin pages.
Personal AI agents such as Grok Bot, Meta Muse, OpenClaw, Instinct, and Poke act on your behalf. If yours can attach a remote MCP server by URL, or make plain HTTP requests, it can place calls, send texts, and read the results through Bland with no code on your side. Pair it with the Agent Phone Plan and the agent gets a dedicated number of its own. There are two ways to connect, depending on whether you already have a Bland account.

​
Prerequisites

  • An assistant that can add a custom MCP server by URL (Grok Bot, for example, has MCP connectors in its bot settings), or that can make HTTP requests on its own.
  • A payment card for the Agent Phone Plan ($29.99/month, includes a US phone number). Without it, the agent can still use numbers already on your account.

​
Option 1: You have a Bland API key

  1. In your assistant, open its MCP or connector settings and add a custom server with this URL:
  2. Add one header, using your API key from the dashboard:
  3. Ask the assistant to make a call:
To give the assistant its own number, so it can receive calls and send texts, subscribe to the Agent Phone Plan at Billing & Plans. The plan provisions a US number within a few seconds. Ask “what’s my Bland phone number?” and the assistant reads it from your account and uses it from then on.

​
Option 2: Let the agent sign itself up

If you do not have a Bland account, the agent can request its own access through a device-authorization flow: it shows you a link and a short code, you sign up and subscribe in your browser, and the agent receives an API key and phone number without you ever handling the key. Paste this into your assistant:
The agent starts the flow, sends you a link and a short code, and waits. Open the link, sign up or sign in, subscribe to the Agent Phone Plan, and approve the request. The agent receives its own API key and phone number, connects the MCP server, and is ready to call and text. The key is scoped to a new organization that belongs to you. Revoke it any time from Settings > API Keys. If your assistant cannot add MCP servers on its own, ask it for the key and add the server yourself as in Option 1. Agents that run on a machine with Node.js can skip the HTTP calls and run the Bland CLI’s MCP server instead, which exposes the same flow as two tools. See the Agent onboarding API.

​
What the agent can do

On the Agent Phone Plan, calls and texts are limited to US and Canadian numbers, one call at a time, up to 60 minutes per call, and up to 100 texts a day. See Limits.

​
Two-way texting

A text is a conversation. When the other side replies, Bland answers from the agent’s number automatically, using the number’s texting prompt. A new plan number starts with a generic prompt, so before asking the agent to run a text thread with a goal, have it set the prompt for that goal:
The agent does this with one API call, Update SMS Configuration:
The prompt belongs to the number, not to one conversation, so it applies to every thread on that number until it is changed. Set it again for the next task.

​
Troubleshooting

​
Building your own agent loop

If you are writing the agent yourself rather than configuring an off-the-shelf assistant, the REST API is a shorter path than MCP. Start with the Agent quickstart for the call lifecycle in three requests, then Call recipes for agents for voicemail, proper nouns, and escalating to a human.

​
Next steps

Agent Phone Plan

What’s included, limits, and how to cancel.

Agent onboarding API

The device-authorization flow in detail: endpoints, statuses, and error codes.

Bland MCP Server

How authentication works and what the server exposes.

Tool reference

Every tool the server exposes.
Docs for agents: llms.txt