Fax.Plus
Server Details
Send and receive faxes from any MCP-compatible AI assistant using the Fax.Plus API
TDQS
Scored across 38 tools
Most tools target distinct resources and actions: contacts vs. groups vs. faxes vs. outbox vs. numbers vs. files, with explicit single/bulk/outbox variants. The main ambiguity is the fax-sending pipeline spread across pipeline_start, request-file-from-user, upload-file, send-fax-uploaded, and resend-fax, whose boundaries require careful reading.
Nearly all tools use a predictable kebab-case verb-noun pattern such as list-contacts, create-contact, update-fax, and bulk-update-outbox-faxes. The main deviation is pipeline_start, which uses an underscore instead of the otherwise consistent hyphenated style.
At 38 tools, the surface is large for a fax API and includes many granular CRUD and pipeline helpers. While most tools map to real operations, the count exceeds a well-scoped range and increases selection burden for an agent.
Coverage is strong across contacts, contact groups, fax records, outbox faxes, file/report retrieval, number assignment, and account metadata. Minor gaps remain, such as no single get-contact operation and only limited lifecycle support for numbers and corporate members.
Publisher details
- Operator
- Alohi
- Operator website
- https://www.fax.plus/
- Vendor relationship
- First-party
- Documentation
- https://apidoc.fax.plus/get-started/fax-plus-mcp · Publisher source
- Privacy policy
- Not provided
- Trust center
- https://www.alohi.com/trust · Publisher source
- Restrictions
- You should have Fax.Plus account to use MCP connector
Available Tools
38 toolsbulk-update-faxesBulk update faxesADestructiveInspect
Update multiple fax records in one request (is_read and/or comment).
Side effects: modifies multiple fax records.
Inputs: payload (required), user_id. Returns: results
bulk-update-outbox-faxesBulk update outbox faxesADestructiveInspect
Update comment for multiple queued outbox faxes in one request.
Side effects: modifies multiple outbox records.
Inputs: payload (required), user_id. Returns: results
create-contactCreate contactAInspect
Create a new contact in Fax.Plus address book. Requires name and fax_number (E.164, e.g. +15551234567). Optional groups must be group names (e.g. Vendors), not group IDs.
Side effects: creates contact; optional shared discloses it to corporate members.
Inputs: name (required), fax_number (required), email, notes, +5 more. Returns: id, name, email, notes, +8 more
create-contact-groupCreate contact groupAInspect
Create a contact group (Fax.Plus tag) to organize contacts. When assigning contacts via set-contact-groups / create-contact / update-contact, pass this group's name, not its id.
Side effects: creates contact group; optional shared discloses it to corporate members.
Inputs: name (required), notes, shared. Returns: id, name, notes, is_shared, +2 more
delete-contactDelete contactADestructiveInspect
Delete a contact. This is destructive and requires explicit confirmation.
Side effects: deletes contact.
Inputs: contact_id (required), confirmation_text (required). Returns: deleted, contact_id
delete-contact-groupDelete contact groupADestructiveInspect
Delete a contact group (Fax.Plus tag). This is destructive and requires explicit confirmation.
Side effects: deletes contact group.
Inputs: group_id (required), confirmation_text (required). Returns: deleted, group_id
delete-faxDelete faxBDestructiveInspect
Delete a fax record. This is destructive and requires explicit confirmation.
Side effects: deletes fax record.
Inputs: fax_id (required), confirmation_text (required), user_id. Returns: fax_id, deleted, user_id
delete-outbox-faxDelete outbox faxADestructiveInspect
Delete a queued outbox fax record. This is destructive and requires explicit confirmation.
Side effects: deletes outbox fax record.
Inputs: outbox_fax_id (required), confirmation_text (required), user_id. Returns: deleted, user_id, outbox_fax_id
get-faxGet a fax recordARead-onlyIdempotentInspect
Get details for a specific fax record. A 404 immediately after send-fax-uploaded can mean the record is not visible yet, not that the send failed.
Side effects: none (read-only).
Inputs: fax_id (required), user_id. Returns: id, to, cost, file, +20 more
get-fax-reportGet fax confirmation reportARead-onlyIdempotentInspect
Return a short-lived URL for the fax confirmation report (PDF). Save that URL to a file on disk immediately. Do not paste the report bytes into the conversation. Open the saved PDF when the user wants to view it.
Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
Inputs: fax_id (required), user_id. Returns: url, expiration_seconds
get-fax-thumbnailGet fax thumbnailARead-onlyIdempotentInspect
Retrieve a fax thumbnail image.
Side effects: none (read-only); returns base64 image bytes in structured output.
Inputs: fax_id (required), user_id. Returns: data_base64, content_type
get-fileDownload fax fileARead-onlyIdempotentInspect
Return a short-lived URL for a sent or received fax file (pdf or tiff). Save that URL to a file on disk immediately. Do not paste the file bytes into the conversation. Open the saved file when the user wants to view it.
Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
Inputs: fax_id (required), format, user_id. Returns: url, expiration_seconds
get-file-pageDownload single fax pageARead-onlyIdempotentInspect
Return a short-lived URL for one fax page as a one-page PDF. Save that URL to a file on disk immediately. Do not paste the page bytes into the conversation. Open the saved PDF when the user wants to view it.
Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
Inputs: fax_id (required), page_num (required), user_id. Returns: url, expiration_seconds
get-member-detailsGet member detailsBRead-onlyIdempotentInspect
Get a corporate member's role and faxing quota.
Side effects: none (read-only).
Inputs: member_user_id (required). Returns: role, quota
get-numberGet number informationBRead-onlyIdempotentInspect
Get information about a specific fax number.
Side effects: none (read-only).
Inputs: number (required), user_id. Returns: id, number, status, owner_id, +6 more
get-outbox-faxGet outgoing faxARead-onlyIdempotentInspect
Get details of a fax scheduled for sending (outbox). A 404 immediately after send-fax-uploaded can mean the record is not visible yet, not that the send failed.
Side effects: none (read-only).
Inputs: outbox_fax_id (required), user_id. Returns: id, ip, to, src, +18 more
get-planGet user planBRead-onlyIdempotentInspect
Get the plan type and admin/owner flags for a user.
Side effects: none (read-only).
Inputs: user_id. Returns: is_admin, is_owner, plan_type
get-token-infoGet token informationARead-onlyIdempotentInspect
Get metadata about the current access token (type, scopes, expiration, etc.).
Side effects: none (read-only).
Returns: id, name, scopes, preview, +4 more
get-userGet account informationBRead-onlyIdempotentInspect
Get account information for a user.
Side effects: none (read-only).
Inputs: user_id. Returns: uid, name, email, phone, +10 more
list-contact-groupsList contact groupsBRead-onlyIdempotentInspect
List contact groups (Fax.Plus tags) with optional pagination and filters.
Side effects: none (read-only).
Inputs: ids, group, limit, offset, +1 more. Returns: records, total_count
list-contactsList contactsARead-onlyIdempotentInspect
List contacts with optional filters (name, fax_number, groups, note), pagination, sorting, and shared/personal filter. Use name=Jane (or fax_number=...) to filter; do not list everything and filter client-side. When sending a fax, always call this after pipeline_start and list-numbers (optional pipeline_id; use limit 20) before request-file-from-user. Do not ask the user for a contact. Response groups are group names (API stores IDs; this tool resolves them).
Side effects: none (read-only).
Inputs: ids, name, note, sort, +7 more. Returns: records, total_count
list-faxesList fax recordsCRead-onlyIdempotentInspect
List fax records for a user. Returns paginated results.
Side effects: none (read-only).
Inputs: category (required), after, limit, order, +11 more. Returns: count, limit, offset, records, +2 more
list-membersList corporate membersBRead-onlyIdempotentInspect
List all corporate members in your account.
Side effects: none (read-only).
Returns: members
list-numbersList phone numbersARead-onlyIdempotentInspect
List your purchased or assigned phone numbers. When sending a fax, always call this after pipeline_start (optional pipeline_id) before request-file-from-user. Do not ask the user to pick a number.
Side effects: none (read-only).
Inputs: user_id, pipeline_id. Returns: numbers
list-outbox-faxesList faxes in the outboxBRead-onlyIdempotentInspect
List faxes in the outbox that are waiting to be sent.
Side effects: none (read-only).
Inputs: user_id. Returns: records
pipeline_startStart a pipelineARead-onlyInspect
Starts a new pipeline and returns its pipeline_id. Call this first when sending a fax; pass the returned id to every subsequent pipeline tool, and optionally to list-numbers / list-contacts.
Side effects: none (mints a handle; writes no state).
Inputs: no named parameters. Returns: pipeline_id
request-file-from-userUpload fax filesADestructiveInspect
Call pipeline_start first, then list-numbers and list-contacts (limit 20), then this tool — always that order. Pass pipeline_id here unchanged. Pass numbers from list-numbers and contacts from list-contacts on this call so the UI can show pickers. Do not re-list inside this tool. Do not ask the user for a sender or destination. Pass optional to/from only if the user already named a number or contact (prefill); omit them otherwise. Prefill to is an array of {number, optional name}; include name when the destination is a contact. from is a number only. Never ask the user to attach the file in chat, and never expect the document to arrive as a chat attachment. NEVER read file contents and NEVER pass base64 or file bytes. Always pass start_file_upload=true and the same pipeline_id. Returns one of three chat payloads. MCP Apps (no mode): widget token in structuredContent; the UI uploads and sends. Do not call send-fax-uploaded or upload-file. mode=unconfirmed: client did not announce Apps support. Relay the user notice, continue as if the UI is present, and use the curl recipe in the same payload only after the user confirms no panel appeared. mode=agentic: client has no Apps support. Follow the curl recipe (POST fax_file), then call send-fax-uploaded with the returned path. Never paste file bytes or base64. The UI does not send a chat message when it sends the fax; it adds the submitted fax ids to the conversation context. When a fax_id is known, call get-fax or get-outbox-fax.
Side effects: mints a short-lived fax-scoped access token; opens the upload UI when the client supports MCP Apps, and that UI uploads the file and sends the fax to the chosen recipient numbers when the user clicks Send.
Inputs: numbers (required), contacts (required), pipeline_id (required), start_file_upload (required), +3 more. Returns: mode, token, method, message, +7 more
resend-faxResend fax from existing faxBDestructiveInspect
Queue a new outbound fax by reusing an existing fax file reference via from_fax. to must be an array of destination numbers.
Side effects: queues outbound fax for delivery.
Inputs: to (required), from (required), from_fax_id (required), comment, +7 more. Returns: ids
send-fax-uploadedSend fax from uploaded filesADestructiveInspect
Queue a new outbound fax using storage paths. Call this after an agentic request-file-from-user curl (files = path from the files POST JSON) or after upload-file. Do not call this after the MCP Apps UI flow — the widget already sent. Pass paths here with to/from and optional send_time. Do not pass local filesystem paths or file bytes. to must be an array. The same paths may be reused for multiple sends. Success means queued/submitted only—not delivered. Status can be checked with get-fax or get-outbox-fax using the returned id.
Side effects: queues outbound fax for delivery.
Inputs: to (required), from (required), files (required), pipeline_id (required), +7 more. Returns: queued, fax_ids, message
set-contact-groupsSet contact groups for contactsADestructiveInspect
Assign contacts to contact groups (Fax.Plus tags). Pass group names (e.g. Vendors), not group IDs from create-contact-group. This overwrites previous group assignments for the selected contacts. If a model passes a group ID by mistake, this tool resolves it to the group name before calling the API.
Side effects: updates contact-group associations; optional shared discloses them to corporate members.
Inputs: contact_ids (required), groups, shared. Returns: object
update-contactUpdate contactADestructiveInspect
Partially update an existing contact. Omit fields you want to keep; only set fields to change. The Fax.Plus API uses PUT (full replace), so this tool loads the contact, merges your fields, and writes the full record back - omitted fields are preserved. If setting groups, use group names (e.g. Vendors), not group IDs.
Side effects: modifies contact.
Inputs: payload (required), contact_id (required). Returns: id, name, email, notes, +8 more
update-contact-groupUpdate contact groupBDestructiveInspect
Update a contact group (Fax.Plus tag).
Side effects: modifies contact group.
Inputs: payload (required), group_id (required). Returns: id, name, notes, is_shared, +2 more
update-faxUpdate faxCDestructiveInspect
Update a fax record's read state and/or comment.
Side effects: modifies fax record metadata.
Inputs: fax_id (required), payload (required), user_id. Returns: fax_id, updated, user_id
update-numberAssign number to memberADestructiveInspect
Assign a fax number to a corporate member (adds them to assigned_to). user_id is the number owner/account context (usually self for the admin). payload.assigned_to is the member user ID to assign TO.
Side effects: adds a member to the number's assigned_to list and notifies them by email and push.
Inputs: number (required), payload (required), user_id. Returns: number, updated, user_id
update-outbox-faxUpdate outbox faxADestructiveInspect
Update a queued outbox fax (comment only).
Side effects: modifies outbox record metadata.
Inputs: payload (required), outbox_fax_id (required), user_id. Returns: updated, user_id, outbox_fax_id
upload-fileUpload fileAInspect
Upload document bytes as base64, then call send-fax-uploaded with the returned path.
Side effects: stores file for fax delivery.
Inputs: file_name (required), pipeline_id (required), file_content (required), format, +2 more. Returns: path
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.