Can I check the source of a specific call using the agent?

Yes! Use the `get_call_details` tool with the Call ID. Your agent will fetch the detailed metadata, which typically includes the `source` or `tracking_number` associated with the call.

How do I list all the leads from my website forms?

Simply ask the agent to `list_form_submissions`. It will retrieve the latest leads captured through web forms from your CallRail account, including names and submission times.

Does the integration allow creating a new tracking number?

The current toolset focuses on querying and monitoring (Read-Only) for marketing attribution analysis. Provisioning new numbers or changing core routing should be managed via the CallRail administrator dashboard.

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

Name: CallRail
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to CallRail through Vinkius, pass the Edge URL in the `mcps` parameter and every CallRail 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="CallRail Specialist",
    goal="Help users interact with CallRail effectively",
    backstory=(
        "You are an expert at leveraging CallRail 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 CallRail "
        "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 CallRail MCP Server

Connect your CallRail account to any AI agent and orchestrate your call tracking, lead management, and marketing attribution workflows through natural conversation.

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

Call Oversight — List all tracked phone calls and retrieve detailed metadata, including durations, tracking numbers, and statuses.
Lead Management — Access leads generated via web forms and monitor their conversion journey directly from your workspace.
Company Coordination — List and retrieve detailed profiles for all companies and clients managed within the account.
Tracker Oversight — Monitor all active tracking numbers and their respective sources to ensure data accuracy.
User & Team Management — Access your directory of users and agents to maintain visibility across your organization.
Alert Monitoring — Retrieve and monitor active account alerts to stay on top of critical issues.

The CallRail 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 CallRail to CrewAI via MCP

Follow these steps to integrate the CallRail 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 CallRail

Why Use CrewAI with the CallRail MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CallRail 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

CallRail + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries CallRail 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 CallRail, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain CallRail 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 CallRail against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

CallRail MCP Tools for CrewAI (10)

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

get_account_info

Retrieve core account information

get_call_details

Get details of a specific phone call

get_company_details

Get details of a specific company

list_alerts

List active account alerts

list_calls

List all tracked phone calls

list_companies

List all companies associated with the account

list_form_submissions

List leads generated via web forms

list_tags

List all lead and call tags

list_trackers

List all tracking numbers and sources

list_users

List all users in the account

Example Prompts for CallRail in CrewAI

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

"List all my calls from today in CallRail."

"Show the details for form submission with ID 99283."

"List all the companies in my CallRail account."

Troubleshooting CallRail MCP Server with CrewAI

Common issues when connecting CallRail 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.

CallRail + CrewAI FAQ

Common questions about integrating CallRail 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.