Bring Cloud Fax
to VS Code Copilot
Learn how to connect iFax to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the iFax MCP Server?
Connect your iFax account to any AI agent and manage fax communications through natural conversation.
What you can do
- Send Faxes — Transmit documents to fax numbers worldwide with delivery confirmation
- Track Status — Monitor real-time delivery status of sent faxes
- Fax History — Browse all sent and received faxes with timestamps and status
- Cancel Pending — Cancel faxes that haven't been transmitted yet
- Resend Failed — Retry failed fax transmissions automatically
- Download Documents — Retrieve received fax documents as files
How it works
1. Subscribe to this server
2. Enter your iFax API Key
3. Start managing faxes from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Healthcare — send HIPAA-compliant faxes for medical records and prescriptions
- Legal Teams — transmit contracts, filings, and signed documents
- Operations — automate fax workflows for compliance and document exchange
Built-in capabilities (6)
Cancel a pending fax
Download a fax document
Check fax delivery status
List sent faxes
Resend a failed fax
Pass faxData as a JSON string containing the file metadata and base64 content. Send a new fax
Why VS Code Copilot?
GitHub Copilot Agent mode brings iFax data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 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
iFax in VS Code Copilot
iFax and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect iFax 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 iFax in VS Code Copilot
The iFax 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 6 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
iFax for VS Code Copilot
Every tool call from VS Code Copilot to the iFax MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send a fax to any number worldwide?
Yes. The send_fax tool transmits a document to any fax number. Provide the destination number in international format and the document content. Use get_fax_status to track delivery confirmation in real-time.
Can I retry a failed fax transmission?
Yes. Use resend_fax with the original fax ID to retry a failed transmission. Use list_faxes to see all faxes and their status, then identify failed ones for retry.
How does iFax API authentication work?
iFax uses a custom accessToken header (not standard Bearer) for authentication. Your API key from the iFax dashboard is sent in all requests to api.ifaxapp.com/v1.
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.