Bring Sms Marketing
to AutoGen
Learn how to connect CallFire to AutoGen 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 AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use CallFire tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use CallFire tools to solve complex tasks
- —
Role-based architecture lets you assign CallFire tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive CallFire tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes CallFire tool responses in an isolated environment
CallFire in AutoGen
CallFire and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CallFire to AutoGen 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 AutoGen
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 AutoGen 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 AutoGen
Every tool call from AutoGen 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 AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call CallFire tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"