Fax from Claude
Connect FaxDash to Claude, ChatGPT, or any app that speaks the Model Context Protocol, and send a fax by asking for it. It uses your own FaxDash account, your own credits, and your own fax history.
Using Claude? Add it in one click.
Opens Claude with the connector details filled in. You still sign in and approve.
Add FaxDash to ClaudeConnect your assistant
Every client asks for the same thing — this address, over streamable HTTP:
https://api.faxdash.io/mcp
- Use the button above, or open Settings → Connectors.
- Click Add, then Add custom connector.
- Name it FaxDash and paste the address into the URL field.
- Click Continue, then Connect. Claude sends you to the FaxDash sign-in page.
- Sign in as you would in the app, then approve the permissions.
- Open Settings → Plugins (the page that manages plugins, skills and MCPs).
- Click Add, then Add MCP server.
- Name it FaxDash and set Type to Streamable HTTP, not STDIO.
- Paste the address into the URL field and connect.
- Sign in to FaxDash and approve the permissions.
- Open Connectors and click New Connector.
- Choose Custom from the list.
- Name it FaxDash and paste the address into Server URL.
- Click Add Connector, then sign in to FaxDash and approve the permissions.
claude mcp add --transport http faxdash https://api.faxdash.io/mcp
Your browser opens for sign-in the first time the connector is used.
codex mcp add faxdash --url https://api.faxdash.io/mcp codex mcp login faxdash
The login command opens your browser to sign in.
grok mcp add --transport http faxdash https://api.faxdash.io/mcp
Then authorise it from inside Grok:
- Run
grok. - Enter
/mcps. - Select faxdash.
- Press i to start authentication, then sign in to FaxDash in your browser.
Check it worked:
grok mcp list grok mcp doctor faxdash
Do not add an Authorization header by hand. Grok handles the OAuth flow and stores the credentials itself.
gemini mcp add --transport http faxdash https://api.faxdash.io/mcp
Gemini notices the server wants OAuth and opens your browser to sign in the first time it is used.
Editing ~/.gemini/settings.json by hand instead? Use httpUrl, not url — in Gemini's config those mean different transports, and url is server-sent events, which this server does not speak:
{
"mcpServers": {
"faxdash": { "httpUrl": "https://api.faxdash.io/mcp" }
}
}Point the client at the address above using streamable HTTP. Authentication is OAuth 2.0, and the server supports both dynamic client registration and client ID metadata documents, so most clients configure themselves with nothing but the URL.
Ask for what you want
Once connected, ordinary requests work:
- “Fax this signed lease to (415) 555-0142.”
- “Did that fax go through?”
- “How many fax credits do I have left?”
You need a PDF the assistant can read, and enough credits. Sending costs one credit per page within the US and Canada, two per page elsewhere.
What it can do
| Tool | What it does |
|---|---|
| send_fax | Sends a PDF to a fax number. Spends credits. |
| get_fax_status | Checks whether a fax was delivered. |
| list_faxes | Lists your recent faxes. |
| get_credits | Reads your credit balance. |
| buy_credits | Returns a checkout link for you to open. The assistant never pays. |
What it cannot do
- It cannot spend money. Buying credits returns a Stripe checkout link for you to open yourself. No payment happens without you completing it.
- It cannot reach the rest of your account. Received faxes, stored documents, contacts, phone numbers and settings are all refused. Only the tools above are reachable.
- It cannot connect without you. Every connection needs your sign-in, your second factor if you use one, and your explicit approval of each permission.
Permissions you approve
- Send faxes on your behalf — spends credits from your balance.
- View your fax history — recipients, status and dates.
- View your credit balance.
- Start a credit purchase — creates a checkout link only.
The approval screen lists exactly these before anything is granted.
Disconnecting
Remove the connector in your assistant, which stops it immediately. Faxes already sent stay in your history, and spent credits are not refunded, exactly as with the app.
Privacy and security
- Sign-in uses OAuth 2.0. Your password is never shared with the assistant.
- Access is limited to the permissions you approve, and every request is checked against them.
- Documents are encrypted in transit and at rest, the same as faxes sent from the app.
- See our Privacy Policy and Terms. Handling health information? See HIPAA.
Trouble connecting
- It asks for a code. Your account has two-factor authentication on. Enter the code as you would in the app.
- Sending fails for lack of credits. Ask for a purchase link, or buy credits in the app.
- Still stuck? Email support@faxdash.io.