Skip to main content
PayPerFax runs a remote MCP server, so an AI app can prepare a fax from inside the chat. The person opens the link that comes back, checks the preview with the price, and pays in the browser. The main-site page is payperfax.com/fax-mcp/. The plain-language page for the assistant is the agents page. Not a developer? Read Can ChatGPT or Claude send a fax for me?

Server

Remote, Streamable HTTP, no authentication. Add it to the AI app as a custom connector.
Nothing is sent and nothing is charged before the person pays. The MCP server cannot pay; the person pays through the link, in the browser. A failed fax is not charged.

Add the server to your AI app

The exact steps depend on the app. In most apps that support MCP:
1

Open the connector settings

Look for a section named “Connectors”, “Integrations”, “MCP servers”, or “Tools”. Claude supports custom connectors. ChatGPT allows them only on some plans or in developer mode, and the Gemini app does not offer them to most consumers yet. Coding agents (Claude Code, Codex, Cursor) add the server in their MCP settings. Availability changes by plan, so check the app’s help pages.
2

Add a custom MCP server

Choose “Add a custom MCP server” (the wording varies). Enter a name (“PayPerFax”) and the URL https://fax.payperfax.com/mcp. The transport is Streamable HTTP, with no authentication.
3

Enable it in the chat

Turn the connector on for the chat where you want to send the fax. The three tools (create_fax, get_fax_status, list_supported_formats) are then available to the assistant.

Tools

create_fax returns the same two kinds of result as the HTTP create request: a complete draft with id, url, and status_url, or a form link (url only) when file_expected is true. Give url to the person. The preview link expires after 4 hours; the form link after 24 hours. Call get_fax_status when the person asks about the fax; do not poll continuously from a chat. For a form link, there is no id in the result. After payment, the person’s confirmation page shows a tracking prompt with the status address, which the person can give to the assistant.

A server for status only

An app that only tracks a fax can use a second server, which has only get_fax_status:
It takes the id or the status address, and returns the values of Check the status. It has the same transport as the main server and no authentication. It has no tools to prepare or pay for a fax.

No file transfer over MCP

The MCP server cannot receive a document from the assistant as a file. There are two alternatives:
  • The assistant writes the document. It sends the text in the markdown field. The text becomes letter.md, the first document of the fax. Headings, lists, tables, and code are kept; raw HTML prints as text. The text can be at most 100 KB.
  • The person has the file. The assistant calls create_fax with file_expected: true. The url in the result opens the pre-filled web form with the notice “Your AI assistant prepared this fax”. The person adds the file (a signed form, a scan, a PDF) and continues in the browser.
A coding agent with a shell (Claude Code, Codex, Cursor) can also send a local file with the HTTP create request as multipart/form-data. AI chat apps do not make that request. The MCP server and the HTTP API are the same service.

The country field

Each MCP request reaches PayPerFax from the AI app’s own server, not from the person’s device, so the caller’s IP address says nothing about the person’s country or currency. Set country on create_fax to the person’s two-letter country code (ISO 3166-1 alpha-2): US, DE, GB, JP, and so on. It sets the currency of the price on the preview, and the date format on the cover page and in the emails. Without it, the price is in US dollars and dates use the US format. Set language to one of en, es, de, fr, it, ja, ko for the language of the preview, the payment page, and the emails.

Limits

  • Requests: each client address can send a limited number of MCP messages per minute. Each message counts (the handshake, the tool list, a tool call), and the two servers share one count. The limit is high, because the requests of all users of an AI app come from that app’s few server addresses. Over the limit, the response is a 429 with Retry-After.
  • Drafts: the number of preview drafts per hour is capped for all callers together. Above the cap, create_fax returns a form link instead of a preview link. That is not an error: the result text says which kind of link it is, and the person continues on the form.

Test with a free test fax number

To check the whole path before a real fax, send a test page to a free test number of Faxbeep. Faxbeep only receives: it shows each test publicly for 30 days, so do not send a private document. When the Faxbeep MCP server is connected too, your assistant can find the test and read its page count.

What this is not

  • No accounts, no API keys, no sign-up.
  • No webhooks, no callbacks, no fax list, no inbound fax.
  • No way to pay without a person. The person pays through the link.
  • Not an “email to fax” subscription product.
You can build PayPerFax into an app, as long as a person checks and pays for every fax. A system that needs unattended or high-volume sending (for example, thousands of referral faxes a day from a healthcare platform) needs a different service. Say so to the person who asks you to build one.

Page for AI assistants

The rules in plain language

Send a fax

The fields of create_fax, as an HTTP request

Check the status

Status values and polling

Fax a form to the IRS

Worked example with an AI assistant