3,400+ MCP servers ready to use
Vinkius

Bland AI MCP Server for CrewAIGive CrewAI instant access to 12 tools to Analyze Call Transcript, Create Voice Agent, Delete Voice Agent, and more

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Bland AI through Vinkius, pass the Edge URL in the `mcps` parameter and every Bland AI tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Bland AI app connector for CrewAI is a standout in the Superpower category — giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Bland AI Specialist",
    goal="Help users interact with Bland AI effectively",
    backstory=(
        "You are an expert at leveraging Bland AI tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Bland AI "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Bland AI
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Bland AI MCP Server

Connect your Bland AI account to any AI agent and take full control of your hyper-realistic AI-driven phone communication and automated voice workflows through natural conversation.

When paired with CrewAI, Bland AI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Bland AI tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Outbound Call Orchestration — Programmatically initiate high-fidelity phone calls to over 200 countries, providing specific tasks and real-time instructions directly through your agent
  • Voice Agent Architecture — Create and manage persistent AI personas with fixed prompts, voices, and personality settings to maintain a perfectly coordinated brand voice
  • Conversation Intelligence — Access real-time call statuses, retrieve complete high-fidelity transcripts, and access secure recording links for every interaction
  • Post-Call Discovery — Programmatically analyze finished calls to extract specific variables, insights, or sentiment summaries using advanced post-processing tools
  • Infrastructure Monitoring — Access your directory of purchased phone numbers and high-fidelity AI voices to oversee your voice communication ecosystem programmatically

The Bland AI MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Bland AI tools available for CrewAI

When CrewAI connects to Bland AI through Vinkius, your AI agent gets direct access to every tool listed below — spanning ai-voice-agent, automated-calling, conversational-ai, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

analyze_call_transcript

Perform post-call analysis

create_voice_agent

Create a persistent AI persona

delete_voice_agent

Remove an AI persona

get_agent_config

Get agent settings

get_call_details

Get details and transcript for a call

list_available_voices

List high-fidelity AI voices

list_phone_numbers

List purchased phone numbers

list_recent_calls

List recent phone calls

list_voice_agents

List configured AI personas

send_phone_call

Send an outbound phone call using an AI agent

stop_active_call

Stop an ongoing phone call

update_agent_config

Modify agent settings

Connect Bland AI to CrewAI via MCP

Follow these steps to wire Bland AI into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Bland AI

Why Use CrewAI with the Bland AI MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Bland AI through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Bland AI + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Bland AI MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Bland AI for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Bland AI, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Bland AI tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Bland AI against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Bland AI in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Bland AI immediately.

01

"Call '+15551234567' and ask if they are still coming to the meeting today at 3 PM."

02

"Show the transcript and recording for call ID 'call_123'."

03

"List all my persistent voice agents in Bland AI."

Troubleshooting Bland AI MCP Server with CrewAI

Common issues when connecting Bland AI to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Bland AI + CrewAI FAQ

Common questions about integrating Bland AI MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.