Bring Sms Marketing
to VS Code Copilot
Learn how to connect CallFire to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings CallFire data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
CallFire in VS Code Copilot
CallFire and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CallFire to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.