Skip to main content
The Bland MCP server exposes two kinds of tools, plus 3 prompts on API key connections:
  • Dedicated tools cover the common workflows with typed inputs. Some render inline UI in clients that support it, such as the call-log inspector, eval scorecards, and the analytics panel.
  • API Reference tools are one tool per page of the API Reference. Each takes the inputs on its linked page, sends the request as your organization, and returns the API’s JSON under data.
Every tool is scoped to one organization: the one that owns the API key, or the one you chose when you signed in with Bland. Connect with a full-access API key or by signing in. Restricted API keys can’t connect to the MCP server. Access is each tool’s annotation. Read tools never change anything. Write tools have side effects. Destructive tools delete things, spend money, or touch live traffic, so your client should ask you before it runs one. The server doesn’t ask for confirmation itself, so keep your client’s tool-approval prompts on. Sign-in is the scope a sign-in connection needs to call the tool. mcp:write also grants mcp:read. Not offered means the tool isn’t listed over sign-in; use an API key connection for it. None means the tool needs no scope. A full-access API key reaches every tool without scope checks.

Dedicated tools

Agents

Full lifecycle for the Bland Agents platform: versioned, branched, and promoted through dev → staging → production environments.
For Bland Agents builds, migrations, snapshot audits, and simulations, use the Norm plugin (norm@bland). The separate bland@bland plugin covers the v1 pathway workspace.
More agent tools (inbound numbers, experiments, dispositions, migration) are under API Reference tools.

Calls

Choose the call resource before invoking a tool

Follow Choose what runs your call: resolve whether the user wants a dashboard agent, persona, or pathway before sending. Honor an established choice, verify the exact ID and environment or version, and ask before changing routes. create_call does not accept agent_id, agent_version, persona_id, or pathway-version selectors. Do not replace an agent choice with pathwayId just to fit this schema. Use send_call instead. It takes every Send Call field in the same snake_case shape, needs the same calls:create scope over sign-in, and runs the call through exactly one of agent_id, persona_id, pathway_id, or task. For example, after verifying the destination and agent ID:
Over an API key connection, call_bland_api with method: "POST" and path: "/v1/calls" takes the same body. Use list_agents, get_agent, and list_agent_environments to verify an agent and its deployment before calling. If the required tool or route is unavailable, explain the limitation and ask the user how to proceed. Do not silently use a persona or pathway instead. After submission, retain the call_id, check the actual source and destination numbers and resource/version association, and verify agent calls under the intended agent’s Conversations view. The create_call result and call-log widget alone do not establish agent attribution. Report a successful call and an attribution problem separately, without placing a duplicate call.

Analytics

Evals

Knowledge and code

Billing

Both tools take a shared_payment_token (spt_...) that the owner approves in their agent wallet. They need an organization API key and aren’t offered over sign-in. If purchases aren’t enabled for your organization, they return FEATURE_DISABLED.

Documentation

search_bland, query_docs_filesystem_bland, and submit_feedback are passed through from the docs site’s own MCP server (https://docs.bland.ai/mcp). If that server is unreachable, they’re missing from the list.

API passthrough

Over an API key connection, the passthrough pair reaches the entire Bland REST API, including fields a dedicated tool leaves out. Sign-in connections don’t get it; use the dedicated and API Reference tools instead.

Setup

Pathways (Legacy)

These tools work with legacy Conversational Pathways. For new builds, use the Agents tools above.

API Reference tools

Each tool below matches one API Reference page, and most names link to it. Its inputs are that page’s path, query, and body parameters. Endpoints that already have a dedicated tool, such as Stop Call (stop_call) and Call Details (get_call_log), aren’t repeated here. Sign-in connections reach an allowlist of everyday resources. A tool is Not offered over sign-in when its endpoint is outside that allowlist, or when it moves money, mints a key, session, or token, controls live calls, sends stored credentials to a third party, or runs model work Bland pays for.

Agent inbound numbers

Agent versions

Agent checks

Agent experiments

Agent identity

Agent dispositions

Agent library

Migration to agents

Calls API

Batches

SMS

Numbers

Blocked numbers

Custom dialing pools

SIP trunks

Custom Twilio accounts

Knowledge bases

Custom tools

Contacts

Memory

Agent testing

Evals API

Guard rails

Prompts library

Widgets

Live translation

Triage

Account

API keys

Organizations

Agent onboarding

Agent Phone Plan

Prompts (Legacy pathways)

Over an API key connection, clients that support MCP prompts (Claude Code surfaces them as slash commands) also get these prompts. Sign-in connections don’t get them. All three work with legacy pathways through search_bland_docs, get_bland_doc, bland_api_get, call_bland_api, create_call, and get_call_log. For Bland Agents, use the Norm plugin commands instead. Docs for agents: llms.txt