Coming Soon

The Fax MCP Server for AI Agents

The first MCP Server for enterprise fax

Connect Fax.Plus to Claude, ChatGPT, or any MCP-compatible AI client. Your assistant can send, receive, and track faxes through natural language, with one hosted endpoint and no custom integration to maintain. Available on Enterprise plans.

Join the waitlist

Be the first to know about new features and updates.

Thank you!

You are on the waitlist. We will be in touch soon.

Read the MCP docs
Claude ChatGPT Cursor Copilot Gemini
Fax.Plus connected
You
Did I get any faxes today?
Fax.Plus
You received 2 faxes this morning.
📄
+1 415 548 5563 9:38 AM · 23 pages ✓ Delivered
📄
+1 312 555 0142 11:15 AM · 4 pages ✓ Delivered
You
Forward the second one to +1 212 555 0199.
Fax.Plus
Done. Fax sent to +1 212 555 0199.
4 pages · delivered

What your AI assistant can actually do

The Fax.Plus MCP Server gives connected AI clients access to the same actions your team uses in the Fax.Plus dashboard, scoped to a token you control.

How to connect Fax.Plus MCP and send your first fax

Connect Fax.Plus to Claude, ChatGPT, or any MCP-compatible AI client in minutes. Once connected, your assistant can send faxes, check your inbox, track delivery, and manage contacts through natural language, with no separate fax interface to open.

1
Create a Personal Access Token
In your Fax.Plus dashboard, go to Settings > Integrations and create a Personal Access Token. Select the scopes you want to grant your AI assistant.
2
Add the MCP server to your AI client
Open your AI client's MCP configuration and add the Fax.Plus server URL: https://mcp.fax.plus/mcp. Use your Personal Access Token as the Bearer authorization header.
3
Verify the connection
Ask your assistant: "What fax numbers do I have on my account?" A successful response confirms the connection is live.
4
Send your first fax
Describe the task in plain language, for example: "Send this document to +1 415 555 0123 and let me know when it's delivered." Your assistant selects the right Fax.Plus action and returns the result in the same conversation.
5
Check delivery
Ask your assistant: "Was my last fax delivered?" It pulls the delivery status directly from your Fax.Plus account.

Built for the workflows that run on fax

Fax-heavy workflows still run on fax for a reason: the recipient requires it. AI agents with MCP access don't replace that, they remove the manual layer around it.

Prior authorization without the manual follow-up

Healthcare teams spend hours per day chasing fax-based prior authorizations, referrals, and lab orders.

What your AI assistant can do:

  1. Send a payer-specific prior auth request from patient data
  2. Check the inbox for payer responses and flag the outcome
  3. Pull the delivery confirmation when the case file needs it

What your team gains: Faster turnaround, less manual follow-up, and a complete audit trail.

Sample prompt:

Send the prior authorization form to BlueCross at +1 312 555 0142 and let me know when it's confirmed.

Compliance note: HIPAA-eligible workflows run on the same Fax.Plus infrastructure as your dashboard fax activity, with a BAA available on Enterprise.

Filings and signed exhibits, sent from your assistant

Legal teams send and receive faxes daily for court filings, discovery requests, signed exhibits, and signature receipts. Each fax needs a confirmation report attached to the case file, which eats hours per week per paralegal.

What your AI assistant can do:

  1. Send a filing to the court fax number from a prepared PDF and capture the confirmation receipt
  2. Check incoming faxes for signed responses and flag which case file each one belongs to
  3. Pull fax reports for case-file documentation without a separate dashboard trip

What your team gains: Faster turnaround on time-sensitive filings, fewer missed confirmations, and case-file documentation that builds itself.

Sample prompt:Send the motion to dismiss to the Eastern District court fax number, then save the confirmation receipt to the Henderson case folder.

Underwriting, claims, and signed authorizations, faster

Finance and insurance workflows still rely on fax for signed authorizations, claim documents, underwriting packets, and lender exchanges. The fax itself is fast; the manual handling around it is where days get lost.

What your AI assistant can do:

  1. Send a complete underwriting or claims packet to the right lender or carrier and track delivery
  2. Check inbound faxes for returned signed authorizations and route them to the case owner
  3. Resend a queued fax if the first attempt fails, without leaving the assistant

What your team gains: Faster cycle time on signed-document workflows, fewer manual logging steps, and a clean fax record for compliance and audit.

Sample prompts:

  1. Send the loan estimate to the borrower's fax on file and notify me when it's been delivered.
  2. Send the signed claim authorization to State Farm at +1 555 555 0100 and confirm delivery.

Inter-agency fax workflows that don't slow your office down

Government offices, courts, and public records teams handle fax volumes that haven't dropped, even as the rest of the workflow has digitized. Most of the manual time goes to logging, routing, and pulling reports for FOIA-style requests.

What your AI assistant can do:

  1. Send a records request or formal notice to another agency's fax number and capture the confirmation
  2. Check the inbox for incoming agency replies and tag them by case or matter number
  3. Pull fax history reports when a public records request requires evidence of transmission

What your team gains: Less time on inter-agency fax mechanics, audit-ready records of every transmission, and a faster path through high-volume request periods.

Sample prompt:Send the records request to the State Health Department fax number and add the confirmation to case 2026-0147.

Hosted, scoped, audit-ready, no infrastructure to maintain

When the business asks for fax inside an AI workflow, IT usually has two options: build a custom integration per AI tool, or block the request. Both are bad. Custom integrations multiply maintenance work; blocking the request pushes shadow IT.

What your AI assistant can do:

  1. Run as a hosted MCP server with no local component to deploy, monitor, or patch
  2. Authenticate through Personal Access Tokens or OAuth 2.0, with eighteen fine-grained scopes for least-privilege access
  3. Log every action through the same Fax.Plus audit trail as direct API and dashboard activity

What your team gains: One integration that works across every MCP-compatible AI client your organization runs, with token revocation, scope control, and audit trails already in place.

Sample setup (drop-in MCP config):

{
  "mcpServers": {
    "faxplus": {
      "type": "url",
      "url": "https://mcp.fax.plus/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}
Compliance

Is the Fax.Plus MCP Server secure and HIPAA-compliant?

Faxes sent through MCP run on the exact same Fax.Plus stack as your dashboard fax activity. The AI route doesn't change the security model . Your assistant authenticates with a token, scoped to actions you allow, revocable any time.

HIPAA icon

HIPAA

Your sensitive medical information is protected in compliance with HIPAA standards.
ISO 27001 logo

ISO/IEC 27001

Your information is secured following international standards.
AICPA SOC logo

SOC 2

Your data's safety, availability, processing integrity, confidentiality, and privacy is evaluated in this audit.
icon

Data Residency

Choose where your data is stored to meet local regulations.
PCI DSS icon

PCI-DSS

Your payment card data is secured for safe transactions.
Your personal data is protected under European Union, and California state laws.

MCP Server vs REST API: which one fits your workflow

The Fax.Plus MCP Server and the Fax.Plus REST API connect to the same fax infrastructure. MCP is built for AI agents and natural language workflows. The REST API is built for high-volume, programmatic fax automation.

Fax.Plus MCP Server Fax.Plus REST API
Best for AI agents, assistant workflows, and natural-language fax actions Backend systems, scheduled jobs, and high-volume batch faxing
Setup Add one hosted MCP endpoint and authenticate with a token Build API authentication, request handling, retries, and error handling
AI client support Works across MCP-compatible clients such as Claude, Cursor, VS Code, and ChatGPT developer workflows Requires custom tool definitions or wrappers for each AI client
Tool discovery AI clients discover available Fax.Plus tools through MCP automatically Developers define and maintain available API actions manually
Multi-step workflows Agents chain actions like upload, send, check status, and follow up Developers sequence each API call explicitly
Authentication Personal Access Token or OAuth 2.0 with fine-grained scopes API key with full account access
Best when The AI assistant is the user-facing interface A backend system controls the workflow

Fax.Plus MCP Server: built for developers and IT teams

Drop the Fax.Plus MCP server into your existing AI app or agent workflow. One hosted endpoint, no local server to deploy or maintain. Working examples for the Anthropic API and the OpenAI Agents SDK.

1from anthropic import Anthropic
2
3client = Anthropic()
4
5response = client.messages.create(
6    model="claude-sonnet-4-6",
7    max_tokens=1024,
8    mcp_servers=[
9        {
10            "type": "url",
11            "url": "https://mcp.fax.plus/mcp",
12            "name": "faxplus",
13            "authorization_token": "YOUR_PERSONAL_ACCESS_TOKEN"
14        }
15    ],
16    messages=[
17        {
18            "role": "user",
19            "content": "Send the document to +1 415 555 0123 and confirm delivery."
20        }
21    ]
22)
23
24print(response.content)
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    async with MCPServerStreamableHttp(
        params={
            "url": "https://mcp.fax.plus/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
            }
        }
    ) as fax_server:
        agent = Agent(
            name="FaxAssistant",
            instructions="Help users send and manage faxes through Fax.Plus.",
            mcp_servers=[fax_server],
        )
        result = await Runner.run(
            agent,
            "Send the document to +1 415 555 0123 and confirm delivery."
        )
        print(result.final_output)

Frequently Asked Questions

What is the Fax.Plus MCP Server?

Arrow
The Fax.Plus MCP Server is a hosted endpoint that connects AI assistants like Claude and ChatGPT to your Fax.Plus account. Once connected, your assistant can send faxes, check the inbox, track delivery, and manage contacts using natural language. It runs on the same Fax.Plus infrastructure as your dashboard, with no local server to deploy.

Which AI clients work with Fax.Plus MCP?

Arrow
Any MCP-compatible client works, including Claude (web and desktop), ChatGPT developer workflows, Cursor, GitHub Copilot, VS Code, Microsoft Copilot Studio, Gemini, and Windsurf. As new MCP-compatible clients launch, the same Fax.Plus connection works automatically.

How long does setup take?

Arrow
Most teams connect Fax.Plus to their AI client in under five minutes. Create a Personal Access Token in Settings → Integrations, paste the MCP server URL into your AI client's configuration, and ask your assistant to send a real fax.

Is the Fax.Plus MCP Server HIPAA compliant?

Arrow
Yes. Faxes sent through MCP run on the same Fax.Plus infrastructure as your dashboard fax activity. HIPAA workflows are supported on Enterprise with a Business Associate Agreement (BAA), with ISO 27001, SOC 2 Type 2, and AES-256 encryption applied to every fax.

Does my AI assistant see the content of my faxes?

Arrow
Your AI assistant only sees what you share with it during the conversation. The Fax.Plus MCP Server transmits documents through Fax.Plus infrastructure with TLS 1.3+ encryption in transit and AES-256 at rest. Your fax content is never used to train AI models.

Can I limit what an AI assistant can do?

Arrow
Yes. The Fax.Plus MCP Server supports eighteen fine-grained scopes, from read-only inbox access to full fax-send permissions. You select the scopes when you create the Personal Access Token. Revoke the token from Settings → Integrations and the assistant loses access immediately.

How many tools does the Fax.Plus MCP Server expose?

Arrow
The Fax.Plus MCP Server exposes 40+ tools across 8 categories: Accounts, Numbers, Faxes, Files, Outbox, Webhooks, Contacts, and Shop. Your AI assistant can discover available tools automatically and chain them into multi-step workflows.

Can I use Fax.Plus MCP alongside the REST API?

Arrow
Yes. Many enterprise teams run both. MCP is built for AI agents and natural-language workflows, while the REST API handles backend systems, scheduled jobs, and high-volume batch faxing. Both connect to the same Fax.Plus infrastructure.

Your AI can fax now.

Connect Fax.Plus to Claude, ChatGPT, or any MCP-compatible AI client.

Partner with us!

Join our affiliate program and deliver exceptional online faxing solutions to your audience.
Become a Partner