How to Use the CallFire MCP in CrewAI

Q: Can I restrict which CallFire tools my agents can access?

Yes. You can use the MCPServerHTTP class from crewai.mcp and apply a toolfilter. This lets you restrict your crew to only read operations like listwebhooks while blocking write access.

Q: How is CallFire call tracking data secured within CrewAI?

Call details retrieved using getcall or listcalls are held temporarily in the agent's execution context. Vinkius secures this MCP pipeline using ephemeral sandboxes, ensuring your call logs are destroyed the moment your crew finishes its task.

Deploy specialized CrewAI agent teams to monitor CallFire campaigns and coordinate outbound communication.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CallFire MCP to CrewAI

Create your Vinkius account to connect CallFire to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup CallFire with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Campaign Monitoring

This MCP Server exposes broadcast tools like `list_campaigns` to track active voice broadcasts while a reporter agent analyzes the results. Run a coordinated operation where one agent monitors performance and another handles escalations. When anomalies occur, the monitoring agent passes the campaign ID to the analyst agent, who calls `get_campaign` to inspect the configuration. The crew collaborates using shared memory to isolate delivery issues without human intervention.

Collaborative Lead Verification

This MCP Server exposes contact tools like `list_contacts` to gather raw lead data, then hands the list over to a validator agent to verify phone numbers and details. Let your agents work together to clean up outbound lists. The validator agent uses `get_contact` to check individual customer histories before passing the clean list to your sales team. This division of labor ensures your agents only interact with high-quality contact records.

Automated Incident Escalation via MCP Server

This MCP Server exposes webhook tools like `list_webhooks` to confirm call tracking notifications are active and pointing to the correct endpoints. Build a self-healing alert system for your messaging pipelines. If a webhook goes offline, the agent runs `get_webhook` to diagnose the failure payload. It then coordinates with a messaging agent to log the incident and alert your on-call engineers.

Setup guide

Set up CallFire MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke CallFire tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="CallFire Analyst",
    goal="Access and analyze CallFire data via MCP.",
    backstory="Expert analyst with direct CallFire access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent CallFire transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="CallFire Analyst",
        goal="Access and analyze CallFire data via MCP.",
        backstory="Expert analyst with direct CallFire access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent CallFire transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CallFire. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect CallFire now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about CallFire MCP in CrewAI

You pass your Vinkius MCP endpoint URL directly to the agent's `mcps` parameter during initialization. This grants that specific agent exclusive access to tools like `list_texts` and `get_text`, keeping other agents focused on different tasks.

Absolutely. You can set up a hierarchical crew where a manager agent delegates tasks. One agent lists active calls using `list_calls`, while another agent inspects specific failures using `get_call` and reports back to the manager.

CrewAI agents share a local memory space to prevent duplicate API requests. If Agent A calls `get_contact` to check a lead, Agent B can read that contact's details from the shared memory instead of invoking the tool again.

Yes. You can use the `MCPServerHTTP` class from `crewai.mcp` and apply a `tool_filter`. This lets you restrict your crew to only read operations like `list_webhooks` while blocking write access.

Call details retrieved using `get_call` or `list_calls` are held temporarily in the agent's execution context. Vinkius secures this MCP pipeline using ephemeral sandboxes, ensuring your call logs are destroyed the moment your crew finishes its task.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript