How do I get a Dialpad API Key?

Log in to your Dialpad admin dashboard, navigate to **Admin Settings > My Company > Authentication > API Keys**, and generate a new key with the required scopes.

Can the agent receive SMS messages?

This integration currently focuses on sending SMS and auditing logs. Incoming SMS can be monitored through the call and message logs in your account history.

Does it support international numbers?

Yes, as long as your Dialpad account is configured for international calling/messaging, the agent can send SMS to any valid E.164 formatted number.

Dialpad MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Dialpad
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Dialpad Specialist",
    goal="Help users interact with Dialpad effectively",
    backstory=(
        "You are an expert at leveraging Dialpad 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 Dialpad "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Dialpad MCP Server

Integrate Dialpad, the AI-powered cloud communications platform, directly into your AI workflow. Manage your enterprise telephony, send and receive business SMS, track call logs and statistics, and update agent presence using natural language.

When paired with CrewAI, Dialpad becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Dialpad 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

Messaging Control — Send outbound business SMS to any E.164 formatted number directly from the chat.
Directory Management — List team contacts and retrieve granular profile details for anyone in your organization.
Call Auditing — Access real-time call logs and statistics to track answered, missed, or rejected rings.
Presence Management — Update your availability status and custom markers to coordinate with your team effectively.

The Dialpad MCP Server exposes 10 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.

How to Connect Dialpad to CrewAI via MCP

Follow these steps to integrate the Dialpad MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Dialpad

Why Use CrewAI with the Dialpad MCP Server

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

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

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

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

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

Dialpad + CrewAI Use Cases

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

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

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

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

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

Dialpad MCP Tools for CrewAI (10)

These 10 tools become available when you connect Dialpad to CrewAI via MCP:

dispatch_office_sms

164. Provision a massively scalable JSON Payload rendering outbound Business Texts

get_agent_profile

Enumerate explicitly attached structured rules traversing self-identities

get_person_details

Perform structural extraction of properties driving an explicit Extension

list_call_statistics

Retrieve explicit Cloud logging tracing rejected Call paths

list_ivr_departments

Identify precise active arrays spanning IVR groupings

list_raw_call_logs

Inspect deep internal arrays parsing real-time Telephony

list_team_contacts

164 capacities directly. Identify bounded routing spaces verifying explicit Business Directories

update_presence_status

Mutate global Web boundaries substituting identifying Desktop status strings

upsert_business_contact

Bootstrap an entirely mutable Contact array resolving Dialpad directories

wipe_directory_entry

Irreversibly vaporize explicit contact constraints destroying Dialpad DB links

Example Prompts for Dialpad in CrewAI

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

"Send an SMS to '+1234567890' saying 'Your support ticket is resolved'."

"Show me the missed calls from this morning."

"Set my Dialpad status to 'In a meeting'."

Troubleshooting Dialpad MCP Server with CrewAI

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

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Dialpad + CrewAI FAQ

Common questions about integrating Dialpad MCP Server with CrewAI.

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.

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.

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.

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.

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.