Voice
Bland MCP connector
The Bland connector brings your AI phone calls, recordings, transcripts and voices into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can place, review and stop Bland calls from the tools they already use.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize yesterday's Bland calls by outcome.
Working in Bland with Elaichi
-
List all Bland calls
-
Bland calls list active
-
Get single Bland call by ID
How to connect Bland to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Bland MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Bland MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Bland MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Bland MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Bland MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Bland to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Bland through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Bland is logged.
-
Sales
Call a fresh lead the moment it arrives
Kick off a Bland call down an existing pathway to a new lead, then ask for the transcript and a summary of what they said once the call ends.
-
Support
Find out how a callback went
Pull up a specific Bland call, read the corrected transcript, and check whether the customer's issue was resolved or needs a human follow up.
-
Operations
See what is on the phones right now
List every active Bland call, listen in on one that looks stuck, transfer it to a person, or stop all active calls if a campaign was launched by mistake.
-
Quality
Review recordings without opening a dashboard
Ask for yesterday's Bland calls, run the analysis on the ones that ran long, and collect the recordings that need a second listen.
-
Marketing
Pick and tune the voice for a campaign
Compare the Bland voices available on your account, rate the ones you tested, rename the finalists, and adjust the settings before an outbound push.
-
Engineering
Keep post-call results flowing downstream
Check which Bland post-call webhooks are set up, add one for a new system, and resend a delivery that your CRM missed.
Try asking
- “Summarize yesterday's Bland calls by outcome.”
- “Pull the corrected transcript for last night's longest call.”
- “Which Bland calls are active right now?”
What connecting Bland gets you
6 screens from Elaichi, each doing one job for your Bland account.
Ask Elaichi to work across your apps.
Summarize yesterday's Bland calls by outcome.
Pull the corrected transcript for last night's longest call.
Which Bland calls are active right now?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Bland calls in plain language.
Answers come from live Bland calls, transcripts and recordings, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Bland.
One governed MCP endpoint for Bland, no SDK and no shared API key.
Tool catalog
133 Bland tools land ready to call.
Calls, transcripts, recordings and webhooks are covered without a line of custom code.
Toolboxes
Every team gets its own Bland toolbox.
Support, sales and compliance each work from a toolbox curated for their remit.
Shared connections
Teammates use Bland without touching credentials.
Each Bland connection shows who connected it and which teams and members share it.
Audit log
Every Bland call action is on record.
When, who, what happened, type and resource, appended for each Bland request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Bland digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch calls
Bland
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Bland
Queued
Automations
A schedule turns Bland calls into action.
Six steps fetch calls, group them, draft a digest, await approval, post back.
Bland health
Refreshed 4 minutes ago · every 15 minutes · from the calls collection
Calls
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Calls created
Last 14 days
By team
Share of activity
Support EMEA 34%
Sales US 27%
Quality review 21%
Compliance archive 18%
Collections and dashboards
Bland call health, counted not asked for.
Four metrics, fourteen days of calls created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Bland
All three can connect Bland to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Bland tools | Allow or restrict single Bland tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Bland call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Bland tools for your AI agents
133 tools are ready to call through Elaichi's MCP endpoint the moment you connect Bland, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Bland to Claude?
Connect Bland in Elaichi first: choose the Bland connector, paste in your Bland API key, and it is ready. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register in Bland and no client ID or secret to generate.
Does Bland work with ChatGPT and Cursor as well as Claude?
Yes. Once Bland is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Bland once and every client picks it up.
What can an AI agent actually do with my Bland data?
An agent can place a Bland call down one of your pathways, list active and past calls, pull a recording or corrected transcript, run the call analysis, listen in, transfer a live call to a person, or stop a call. It can also manage your Bland voices and post-call webhooks and check your account details. Because Bland exposes a lot of actions, short concrete asks such as "stop all active calls" work better than long paragraphs.
Does connecting Bland give the AI my whole account?
The agent only gets what the Bland API key you connected can already reach, nothing more. Elaichi can then narrow that further, for example allowing your team to read Bland transcripts and recordings but not place or stop calls. Elaichi never widens access beyond what the key itself allows.
Can I stop an agent from deleting voices or stopping calls in Bland?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Bland voices, stopping calls or placing new ones while leaving transcripts and recordings open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Bland connection when someone leaves?
When you offboard a person in Elaichi, their access to Bland through every AI client ends at once. If they had shared a Bland connection with a team, it keeps working for everyone else. If you want Bland gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Bland MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Bland is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Bland?
Yes. Both let Claude, ChatGPT or Cursor use Bland. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Bland call.
How is Elaichi different from Composio for Bland?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Bland: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Bland in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot