Bring Cloud Fax
to CrewAI
Learn how to connect iFax to CrewAI 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 CrewAI?
When paired with CrewAI, iFax becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call iFax tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
iFax in CrewAI
iFax and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect iFax to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.