Bring Sms Marketing
to LlamaIndex
Learn how to connect CallFire to LlamaIndex and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the CallFire MCP Server?
Connect your CallFire account to any AI agent and manage your voice and SMS communication workflows through natural conversation.
What you can do
- Contact Management — List all contacts and retrieve individual contact profiles with phone numbers and metadata
- Call Tracking — Browse all inbound and outbound calls with duration, status, and call recording details
- SMS History — Review sent and received text messages with delivery status and timestamps
- Campaign Monitoring — List all broadcast campaigns (voice and text) and inspect individual campaign configurations and performance
- Webhook Management — View all configured webhooks and inspect their delivery settings and event triggers
How it works
1. Subscribe to this server
2. Enter your CallFire API Login (username) and API Password from your account settings
3. Start managing your communications from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Teams — check call history, review SMS delivery rates, and monitor campaign reach without leaving the AI workspace
- Marketing Operations — monitor broadcast campaign performance and contact engagement metrics
- Customer Support — quickly search for calls and messages by contact ID for case investigation
Built-in capabilities (10)
Get a specific call
Get a specific broadcast campaign
Get a specific contact
Get a specific text message
Get a specific webhook
List all calls
List all broadcast campaigns
List all contacts
List all text messages
List all webhooks
Why LlamaIndex?
LlamaIndex agents combine CallFire tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine CallFire tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain CallFire tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query CallFire, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what CallFire tools were called, what data was returned, and how it influenced the final answer
CallFire in LlamaIndex
CallFire and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CallFire to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for CallFire in LlamaIndex
The CallFire 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
CallFire for LlamaIndex
Every tool call from LlamaIndex to the CallFire MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query CallFire tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp