CallFire MCP for AI. Manage Outreach, Calls, and Texts from One Chat Window
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
CallFire MCP manages high-volume voice and SMS campaigns directly through your AI agent. Use this connector to run broadcast messages, track call metrics, list contacts, and review complete message history at scale.
It lets you manage all outreach workflows without switching between separate platforms.
What your AI can do
Get call
Retrieves the full details for one specified phone call.
Get campaign
Gets all configuration and results for a single broadcast campaign.
Get contact
Fetches the complete profile details for an individual contact.
List all contacts in your system or retrieve specific profiles, including phone numbers and associated metadata.
Browse detailed records of every call, whether inbound or outbound, noting duration, status, and recording availability.
View a full archive of sent and received text messages, including delivery statuses and timestamps for each one.
List all broadcast campaigns (both voice and text) and inspect their specific configurations and performance metrics.
View configured webhooks, checking delivery settings and the event triggers associated with them.
Ask an AI about this
Waiting for input…
CallFire: Messaging & Communication (10 Tools)
Use these ten tools to manage every aspect of your outreach workflow, from listing all contacts to checking the status of a single webhook.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using CallFire on VinkiusGet Call
Retrieves the full details for one specified phone call.
Get Campaign
Gets all configuration and results for a single broadcast campaign.
Get Contact
Fetches the complete profile details for an individual contact.
Get Text
Retrieves the content and status of a specific text message exchange.
Get Webhook
Shows the configuration details for one defined webhook endpoint.
List Calls
Lists every call record based on specified date ranges or filters.
List Campaigns
Provides an overview and status of all active broadcast campaigns.
List Contacts
Lists every contact record in the system for auditing or segmentation purposes.
List Texts
Provides a list of text messages, showing delivery status and timestamps for review.
List Webhooks
Shows all webhooks set up in the system and their current delivery settings.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with CallFire, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing Outreach Data Used To Be a Dashboard Nightmare
Today, if you want to know how your last marketing campaign went, you have to open five different tabs. You check the Campaign dashboard for delivery rates; then you jump to the Call History tab to see call volume; next, you pull up the Contacts list to figure out who was actually reached; and finally, you dig into SMS logs just to verify replies.
With this MCP, all that data comes through your agent. You simply ask: 'What were the results of the Spring Promo campaign?' Your agent runs multiple checks—it reviews `list_campaigns`, pulls call metrics from `list_calls`, and verifies text delivery using `list_texts`—and it gives you one coherent answer.
Getting Full Context with Calls and Texts
Before, if a sales rep needed to know the full context of an account, they'd have to manually look up the contact ID in one system, then search another for calls, and finally open a third dashboard for message threads. It takes ten minutes just to compile the file.
Now you can ask your agent: 'What is the full history for Contact 8901?' The MCP uses `get_contact`, `list_calls`, and `get_text` simultaneously, delivering a complete, chronological report instantly. You stop hunting through dashboards; you just talk to it.
What your AI can actually do with this
Managing large-scale outreach usually means jumping between a CRM, a messaging dashboard, and a reporting tool just to get a full picture. This MCP changes that by connecting your voice and SMS communications directly into your natural chat flow. You can ask your agent things like, 'Show me all texts sent last week that failed delivery' or 'How many calls did we make to contacts missing phone numbers?' It aggregates data from call logs, message histories, contact records, and campaign performance—all in one conversation thread.
Because this MCP is managed by Vinkius, you just connect your credentials once, and your AI agent gets access to the entire communication catalog, letting you focus on outcomes instead of dashboards.
019dd0c8-fc52-727c-849d-010744c0b3f1 Here's how it actually works
The bottom line is you manage complex, high-volume communications from a single conversational interface, making reporting immediate.
Subscribe to this MCP in Vinkius and enter your CallFire API Login (username) and API Password from your account settings.
Authorize your AI client, like Cursor or Claude, to access the connected communication data.
Ask your agent a question—for example, 'List all contacts that haven't been called this month.' The MCP executes the call and returns the structured data directly.
Who is this actually for?
This tool is built for operational roles that deal with massive amounts of communication data. It's perfect for the sales manager who needs to audit call history quickly, or the marketing ops person tired of running reports across three different dashboards.
Uses this MCP to review specific contact profiles and check recent call records immediately before a client meeting.
Monitors broadcast campaign performance, checking delivery rates for both SMS and voice messages after a major launch.
Investigates service issues by searching through call logs and message history using a specific contact ID to build a case file.
What Changes When You Connect
Audit your entire contact list using list_contacts to quickly identify records that are missing phone numbers or haven't been touched in months. This saves time spent manually cross-referencing spreadsheets.
Track campaign performance by listing all campaigns (list_campaigns), giving you an instant view of broadcast reach and delivery rates without leaving your AI workspace.
Investigate past client interactions using get_call or get_text. You can pull up specific call recordings or message threads instantly, which is critical for support case reviews.
Monitor system connections by running list_webhooks. This ensures that any external tools relying on your communication data are still properly configured and functioning.
Get immediate reporting. Instead of building a custom query to find all calls from last week, you simply ask the agent using list_calls and get actionable metrics back.
See it in action
Auditing poor outreach data
A marketing manager needs to know which contacts haven't received a message in 60 days. They prompt their agent: 'Show me all inactive contacts.' The agent uses list_contacts and filters the results, providing an immediate list of leads ready for re-engagement.
Building a support case file
A customer service analyst gets a complaint. They ask their agent to 'Gather all communications for Contact ID 456.' The agent uses get_call and list_texts, compiling the call transcript, message history, and campaign details into one response.
Checking broadcast health
A marketing team needs to verify if a recent SMS promotion went out correctly. They ask the agent to 'List all campaigns for the Spring Sale.' The agent uses list_campaigns and confirms delivery rates across multiple segments.
Debugging integrations
An integration engineer suspects a webhook isn't firing when calls are made. They prompt the agent to 'List all webhooks related to call events.' The agent uses list_webhooks and shows the exact triggers, allowing for rapid debugging.
The honest tradeoffs
Treating data retrieval like a database query
A user tries to manually write out complex filtering logic: 'Get all calls where status=completed AND duration>10 minutes.' This requires remembering specific API parameters and is error-prone.
Instead, simply ask your agent using list_calls: 'Show me the records for completed calls lasting over 10 minutes last month.' The agent handles the complex filtering logic automatically.
Ignoring communication flow
A user only checks campaign performance but forgets to check if contacts were actually updated after the outreach. They miss key data points.
Always combine tools. Use list_campaigns first, then use get_contact on a few results from that list to confirm which specific people received the message and what their latest profile status is.
Overlooking historical details
A user only checks recent calls but misses important messages exchanged weeks ago, leading to incomplete context.
Don't stop at call history. Use list_texts alongside list_calls. This gives the full picture: what was said on the phone, and what was written afterward.
When It Fits, When It Doesn't
Use this MCP if your core business relies on high-volume communication—specifically mass SMS/voice outreach or detailed post-interaction reporting. You need to audit contact records (list_contacts), review campaign performance (list_campaigns), and consolidate all communications (calls, texts) into one view.
Don't use this if you just need a single piece of data, like checking the status of one webhook or getting a simple list of contacts. For that, the individual get_webhook or list_contacts tools work fine by themselves. But if you want to correlate those pieces (e.g., 'Which contacts received this message and had an incoming call?'), you need the full MCP connecting them all.
Questions you might have
How do I check which contacts are missing phone numbers using the list_contacts tool? +
The agent uses list_contacts and applies filters for incomplete records. It reports back a count of how many contacts lack necessary data, letting you know exactly where your clean-up needs to happen.
Can I check the performance of multiple campaigns at once with list_campaigns? +
Yes. You ask the agent to 'List all campaigns for Q2.' The tool uses list_campaigns and consolidates the results, giving you a side-by-side view of metrics like messages sent and delivery rates.
What is the difference between get_call and list_calls? +
The key difference is scope. Use list_calls when you want an overview, filterable by date or status. Use get_call only when you have a specific call ID and need all its details.
Does the MCP help me debug webhook issues? +
Yes. You can use list_webhooks to see what webhooks are configured, and then use get_webhook if you suspect a specific endpoint is failing its event triggers.
When I use get_text, what information do I get about a failed message? +
The response includes the exact delivery status and the reason for failure. You'll see specific error codes—like 'invalid number' or 'carrier blocked'—which lets you clean up your contact list accurately.
What credentials do I need to connect the MCP and start using list_contacts? +
You must provide your CallFire API Login (username) and API Password, which are found in your account settings. Once connected, your agent can immediately access and manage all stored contact data.
When listing webhooks using list_webhooks, how do I check their triggering events? +
The tool displays the full configuration details for each webhook. You'll see exactly what event or action is set to trigger it, allowing you to verify if the setup matches your workflow needs.
What specific performance metrics does get_campaign provide? +
It gives a deep dive into one broadcast campaign. You retrieve key data points like total messages sent, the overall delivery rate, and counts of replies received for detailed analysis.
Can I review the full history of calls and text messages for a specific contact? +
Yes. Use list_calls to browse all call records and get_call with a specific Call ID for full details including duration, recording URL, and disposition. For SMS, use list_texts to browse messages and get_text for individual message content and delivery status.
Does CallFire require two separate credentials? +
Yes. CallFire uses HTTP Basic Authentication with an API Login (username) and an API Password. Both are generated in your CallFire account under Settings > API Access. They are separate from your dashboard login credentials.
Can I monitor my active broadcast campaigns and their delivery status? +
Yes. The list_campaigns tool retrieves all voice and text broadcast campaigns with their status (active, paused, finished). Use get_campaign with a Campaign ID to inspect configuration details, delivery rates, and audience targeting. Combine with list_webhooks to verify event-driven notifications are configured correctly.
We've already built the connector for CallFire. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.