Fax.Plus MCP Server

The Fax.Plus MCP Server lets AI assistants send and receive faxes, manage contacts, track delivery, and configure webhooks through the Model Context Protocol (MCP) — an open standard for connecting AI tools to external services.

Beta — The Fax.Plus MCP Server is currently in beta. Features, tool schemas, and authentication flows may change. Report issues to support@alohi.com.

Enterprise plan required — Access to the Fax.Plus API requires a Fax.Plus Enterprise plan. The API is not available on Free, Premium, or Business plans.

MCP server URL

https://mcp.fax.plus/mcp

What you can do

The Fax.Plus MCP Server enables AI assistants to interact with your Fax.Plus account using natural language. Here’s what’s supported:

Capability	Description
Send faxes	Upload a document and send it to any fax number worldwide
Receive faxes	Check your inbox for incoming faxes, filter by date or sender
Track delivery	Monitor outbox status and get real-time delivery confirmations
Manage contacts	List, create, update, and organize fax contacts and groups
Manage numbers	View assigned fax numbers, status, and notification settings
Corporate accounts	List and manage corporate team members (admin only)
Webhooks	Configure webhooks for real-time fax event notifications
File uploads	Upload documents for faxing (PDF, TIFF, DOC, and more)

Prerequisites

Before connecting, make sure you have:

An active Fax.Plus Enterprise plan — View pricing
A Personal Access Token (PAT) or OAuth 2.0 credentials — How to create a PAT
At least one fax number assigned to your account

Authentication

Personal Access Tokens (PAT)

PATs provide secure, fine-grained access to the API. Create them from your Fax.Plus dashboard:

Open Integrations

Manage tokens

Under Fax.Plus API, find Personal Access Tokens and click Manage.

Create and configure

Create a new token and select the appropriate scopes for your use case.

Copy your token

Copy the token immediately — it won’t be shown again.

Available scopes

Scope	Access
`fax:all:read`	Read-only access to all fax operations
`fax:all:edit`	Full access to all fax operations
`fax:webhook:read`	View webhook configurations
`fax:webhook:edit`	Create and manage webhooks
`fax:fax:read`	View and list faxes, outbox, files, reports
`fax:fax:edit`	Send faxes, manage outbox and files
`fax:shop:read`	View available fax numbers for purchase
`fax:shop:edit`	Purchase and provision fax numbers
`fax:user:read`	View the current user’s account details (PAT owner)
`fax:user:edit`	Update the current user’s account details (PAT owner)
`fax:member:read`	View corporate member details
`fax:member:edit`	Update corporate member settings
`fax:numbers:read`	List and view assigned fax numbers
`fax:numbers:edit`	Manage and configure fax numbers
`fax:ai:read`	Read access to AI-powered fax features
`fax:ai:edit`	Manage AI-powered fax features
`fax:ai_settings:read`	View AI feature settings and configuration
`fax:ai_settings:edit`	Update AI feature settings and configuration

For most use cases, fax:all:read and fax:all:edit provide the access you need. Use granular scopes when you want to restrict what the integration can do.

OAuth 2.0 (Dynamic Client Registration)

MCP clients with native OAuth support — such as Claude.ai, Claude Desktop, ChatGPT connectors, and Cursor — can connect without creating a PAT manually. The server implements Dynamic Client Registration (DCR) on top of an OAuth 2.0 authorization code flow:

Add the server

In your MCP client, add https://mcp.fax.plus/mcp as a remote server — no token required upfront.

Auto-discovery and registration

The client fetches OAuth metadata from /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, then registers itself via /oauth/register.

Authorize

You’re redirected through /oauth/authorize to log in to your Fax.Plus account and approve access.

Connected

The client exchanges the authorization code for a token via /oauth/token. No manual token copy/paste needed.

Redirect URI allowlist — During registration, the redirect_uri your client supplies must match an allow-listed pattern (for example https://claude.ai/api/mcp/auth_callback, https://chatgpt.com/connector/oauth/*, or http://localhost:* for local development clients). Registration attempts with a redirect URI outside this list are rejected. Contact support@alohi.com if your MCP client needs to be added to the allowlist.

Connecting to an MCP client

The Fax.Plus MCP Server works with any client that supports the Model Context Protocol. Setup depends on your client — not every client accepts the same config format.

Client	Config file	Remote HTTP support
Claude Desktop	`claude_desktop_config.json`	stdio only — use `mcp-remote` or Settings → Connectors
Cursor, Claude Code	`.cursor/mcp.json`, `~/.claude/settings.json`	`"type": "url"` supported
Claude.ai (web)	Settings → Connectors	OAuth via UI — no config file

Clients with native OAuth support only need the server URL (see OAuth 2.0 above). For clients without OAuth discovery, use a PAT with the client-specific configuration below.

Claude Desktop

Claude Desktop’s claude_desktop_config.json only supports stdio MCP servers (command + args). It does not accept "type": "url" — entries without command are ignored and may be removed when Claude Desktop saves the file. Use one of these approaches:

PAT via mcp-remote (config file)
OAuth via Connectors (recommended)

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (or the equivalent path on Windows/Linux):

{
  "mcpServers": {
    "faxplus": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fax.plus/mcp",
        "--header",
        "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      ]
    }
  }
}

mcp-remote runs locally as a stdio process Claude Desktop can talk to, and forwards requests over HTTP to https://mcp.fax.plus/mcp.

Prefer passing the token via env instead of inlining it in args:

{
  "mcpServers": {
    "faxplus": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fax.plus/mcp",
        "--header",
        "Authorization:${FAXPLUS_PAT}"
      ],
      "env": {
        "FAXPLUS_PAT": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}

For OAuth without managing a PAT in a config file:

Open Claude Desktop → Settings → Connectors
Add a custom connector with URL https://mcp.fax.plus/mcp
Complete the Fax.Plus login and authorization flow

Claude Desktop handles the remote HTTP connection directly in this path — no mcp-remote bridge needed.

Do not use "type": "url" in claude_desktop_config.json. That format works in Cursor and Claude Code, but Claude Desktop expects stdio servers only.

Cursor and Claude Code

These clients support direct remote HTTP configuration with a PAT:

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

Using with the Anthropic API (MCP Connector)

import anthropic

client = anthropic.Anthropic()

response = client.beta.messages.create(
    model="claude-sonnet-4-6",
    max_tokens=1024,
    betas=["mcp-client-2025-11-20"],
    mcp_servers=[
        {
            "type": "url",
            "url": "https://mcp.fax.plus/mcp",
            "name": "faxplus",
            "authorization_token": "YOUR_PERSONAL_ACCESS_TOKEN",
        }
    ],
    messages=[
        {"role": "user", "content": "Check my fax inbox for anything received today"}
    ],
)

Using with OpenAI Agents SDK

from openai_agents import Agent, MCPServerSse

faxplus_server = MCPServerSse(
    url="https://mcp.fax.plus/mcp",
    headers={"Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"},
)

agent = Agent(
    name="Fax Assistant",
    instructions="Help the user send and receive faxes.",
    mcp_servers=[faxplus_server],
)

Replace YOUR_PERSONAL_ACCESS_TOKEN with the PAT you created in the Authentication section.

Available tools

The Fax.Plus MCP Server exposes the following tools to connected AI assistants.

Accounts

Tool	Description
`get-token-info`	Get current token metadata/scopes
`list-members`	List corporate members
`get-user`	Get account information
`update-user`	Update account information
`get-member-details`	Get corporate member role/quota
`update-member-details`	Update corporate member role/quota
`invite-members`	Invite corporate members
`resend-invitations`	Resend pending invitations

Numbers

Tool	Description
`list-numbers`	List assigned/purchased fax numbers
`get-number`	Get details for one fax number
`update-number`	Update number assignment
`revoke-number`	Revoke a number (destructive)

Faxes

Tool	Description
`list-faxes`	List fax records
`get-fax`	Get a specific fax record
`update-fax`	Update fax metadata (`is_read` / `comment`)
`delete-fax`	Delete a fax record (destructive)
`bulk-update-faxes`	Bulk update fax metadata
`bulk-delete-faxes`	Bulk delete fax records (destructive)

Files

Tool	Description
`upload-file`	Upload a document for sending
`get-file`	Download fax file (`pdf`/`tiff`)
`get-file-page`	Download single fax page
`get-fax-report`	Get fax confirmation report
`get-fax-thumbnail`	Get fax thumbnail image

Outbox

Tool	Description
`list-outbox-faxes`	List outgoing/queued faxes
`get-outbox-fax`	Get one outgoing fax
`update-outbox-fax`	Update queued outbox fax
`bulk-update-outbox-faxes`	Bulk update queued outbox faxes
`send-fax-uploaded`	Send fax using uploaded file paths
`resend-fax`	Resend using an existing fax as source
`delete-outbox-fax`	Delete queued outbox fax (destructive)
`bulk-delete-outbox-faxes`	Bulk delete queued outbox faxes (destructive)

Webhooks

Tool	Description
`get-webhooks`	List webhooks
`create-webhook`	Create webhook
`delete-webhook`	Delete webhook (destructive)

Contacts

Tool	Description
`list-contacts`	List contacts
`create-contact`	Create contact
`update-contact`	Update contact
`delete-contact`	Delete contact (destructive)
`list-contact-groups`	List contact groups
`create-contact-group`	Create contact group
`update-contact-group`	Update contact group
`delete-contact-group`	Delete contact group (destructive)
`set-contact-groups`	Assign contacts to groups
`share-contacts`	Share contacts with corporate members
`share-contact-groups`	Share contact groups with corporate members

Shop

Tool	Description
`get-balance`	Get account balance
`list-countries`	List countries for number purchase
`list-areas`	List areas for a country
`list-shop-numbers`	List available numbers for purchase
`purchase-number`	Purchase a fax number

Usage examples

Once connected, you can interact with Fax.Plus through natural language. Here are some common workflows.

Send a fax

You: Send the attached contract to +1-212-555-0199

Assistant: I’ve uploaded your contract and sent it to +1-212-555-0199. The fax was delivered successfully — 3 pages, transmitted in 12 seconds. The fax ID is abc123def.

Check your inbox

You: Did I receive any faxes today?

Assistant: You received 2 faxes today:1. From +1-415-548-5563 at 9:38 AM — 23 pages, status: success2. From +1-312-555-0142 at 2:15 PM — 1 page, status: success

Track delivery

You: Did my fax to the courthouse go through?

Assistant: Yes — your fax to +1-218-413-7255 was delivered successfully at 12:14 PM today. 2 pages, 2 seconds transmission time.

Manage contacts

You: Show me all my fax contacts in the Office group

Assistant: You have 1 contact in the “Office_ch” group: Alohi Fax Machine near Scott, fax number +41 22 794 3479.

List fax numbers

You: What fax numbers do I have?

Assistant: You have one active fax number: +1-419-548-5563, acquired October 8, 2024, with email and push notifications enabled.

API reference

The MCP Server is built on the Fax.Plus REST API v3. For detailed endpoint documentation, schemas, and error codes:

API Documentation

Full endpoint reference with request/response examples

Quickstart Guide

Get up and running with the Fax.Plus API in minutes

Authentication

OAuth 2.0 and PAT setup guides

Help Center

FAQs, troubleshooting, and how-to articles

SDKs

Language	Package
Node.js	`@alohi/faxplus-api`
Python	`faxplus-api`

Security and compliance

Fax.Plus is built with enterprise-grade security and meets strict regulatory requirements:

Encryption: AES-256 at rest, TLS 1.3+ in transit
Certifications: ISO 27001, SOC 2 Type 2, HIPAA (with BAA), PCI DSS
Compliance: GDPR, CCPA, eIDAS
Access control: SSO, 2FA, role-based permissions, fine-grained PAT scopes
Data residency: Flexible options across multiple regions
Audit trails: Complete logging of all fax activity

For HIPAA-compliant faxing workflows, see Fax.Plus HIPAA.

Limitations

Current beta limitations

Enterprise plan required — The Fax.Plus API is only available on Enterprise plans.
No account creation via API — New user accounts must be created through the Fax.Plus web dashboard. The API supports managing existing accounts only.
No public sandbox — Contact support@alohi.com to request a test environment.
File size limits — Uploaded files are subject to size limits. Large documents should be split before uploading.
Rate limits — API requests are rate-limited. See the API documentation for current thresholds.
Fax delivery — Transmission success depends on the recipient’s fax machine availability and line quality. Automatic retries can be configured when sending.

Troubleshooting

”Invalid token” or 401 Unauthorized

Your PAT may have expired or lacks the required scopes. Generate a new token from Settings → Integrations → Personal Access Tokens in your Fax.Plus dashboard. Ensure the token includes at least fax:all:read for read operations and fax:all:edit for sending faxes.

Fax stuck in outbox or delivery failed

Check that the recipient’s fax number is in E.164 format (e.g., +12125550199). Verify the number is a working fax line. You can configure automatic retries with the retry parameter when sending.

403 Forbidden on member endpoints

Only corporate admin accounts can access member management endpoints. Verify your account has the corporate_admin role.

”invalid_redirect_uri” during OAuth setup

Dynamic Client Registration rejects any redirect_uri that isn’t on the server’s allowlist. This is expected for MCP clients that haven’t been vetted yet — contact support@alohi.com to request that your client be added.

Claude Desktop ignores my MCP server or removes it from the config

You likely used "type": "url" in claude_desktop_config.json. Claude Desktop only supports stdio servers there. Switch to the mcp-remote configuration above, or add the server via Settings → Connectors instead.

Getting help

Help Center: help.alohi.com
API Support: support@alohi.com
Enterprise Sales: alohi.com/contact-sales

​Fax.Plus MCP Server

​MCP server URL

​What you can do

​Prerequisites

​Authentication

​Personal Access Tokens (PAT)

​Available scopes

​OAuth 2.0 (Dynamic Client Registration)

​Connecting to an MCP client

​Claude Desktop

​Cursor and Claude Code

​Using with the Anthropic API (MCP Connector)

​Using with OpenAI Agents SDK

​Available tools

​Accounts

​Numbers

​Faxes

​Files

​Outbox

​Webhooks

​Contacts

​Shop

​Usage examples

​Send a fax

​Check your inbox

​Track delivery

​Manage contacts

​List fax numbers

​API reference

API Documentation

Quickstart Guide

Authentication

Help Center

​SDKs

​Security and compliance

​Limitations

​Troubleshooting

​”Invalid token” or 401 Unauthorized

​Fax stuck in outbox or delivery failed

​403 Forbidden on member endpoints

​”invalid_redirect_uri” during OAuth setup

​Claude Desktop ignores my MCP server or removes it from the config

​Getting help

Fax.Plus MCP Server

MCP server URL

What you can do

Prerequisites

Authentication

Personal Access Tokens (PAT)

Available scopes

OAuth 2.0 (Dynamic Client Registration)

Connecting to an MCP client

Claude Desktop

Cursor and Claude Code

Using with the Anthropic API (MCP Connector)

Using with OpenAI Agents SDK

Available tools

Accounts

Numbers

Faxes

Files

Outbox

Webhooks

Contacts

Shop

Usage examples

Send a fax

Check your inbox

Track delivery

Manage contacts

List fax numbers

API reference

SDKs

Security and compliance

Limitations

Troubleshooting

”Invalid token” or 401 Unauthorized

Fax stuck in outbox or delivery failed

403 Forbidden on member endpoints

”invalid_redirect_uri” during OAuth setup

Claude Desktop ignores my MCP server or removes it from the config

Getting help