Fax.Plus のリモート MCP サーバーとは何ですか?
Fax.Plus のリモート MCP サーバーは、https://mcp.fax.plus/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
Fax.Plus MCP Server認証済み注目
@Alohi
Fax.Plus MCP Server について
Send and receive faxes from any MCP-compatible AI assistant using the Fax.Plus API
接続情報
https://mcp.fax.plus/mcpセットアップ
claude mcp add fax-plus --transport http https://mcp.fax.plus/mcpFax.Plus MCP Server のツール
53Delete multiple fax records in one request. This is destructive and requires explicit confirmation. Side effects: deletes multiple fax records.
Delete multiple outbox fax records in one request. This is destructive and requires explicit confirmation. Side effects: deletes multiple outbox fax records.
Update multiple fax records in one request (is_read and/or comment). Side effects: modifies multiple fax records.
Update comment for multiple queued outbox faxes in one request. Side effects: modifies multiple outbox records.
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.
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.
Create a webhook subscription for a fax event and target URL. Optionally pass numbers (E.164, e.g. ["+17154578872"]) to fire only for those fax numbers; omit numbers to receive events for all numbers. Side effects: creates webhook subscription.
Delete a contact. This is destructive and requires explicit confirmation. Side effects: deletes contact.
Delete a contact group (Fax.Plus tag). This is destructive and requires explicit confirmation. Side effects: deletes contact group.
Delete a fax record. This is destructive and requires explicit confirmation. Side effects: deletes fax record.
Delete a queued outbox fax record. This is destructive and requires explicit confirmation. Side effects: deletes outbox fax record.
Delete a webhook subscription by ID. This is destructive and requires explicit confirmation. Side effects: deletes webhook subscription.
Get your Fax.Plus shop account balance. Side effects: none (read-only).
Get details for a specific fax record. wait_seconds is optional (default 0). After send-fax-uploaded, pass wait_seconds=30 on the first check so the record can become visible; omit it or pass 0 for later polls. Immediate 4xx without that wait is expected, not a lost job. Tell the user status in everyday words (preparing, sending, sent, failed); do not paste raw fields, costs, or client metadata unless they ask for a support reference. Side effects: none (read-only).
Retrieve a fax confirmation report (PDF). Side effects: none (read-only); returns base64 PDF report in structured output.
Retrieve a fax thumbnail image. Side effects: none (read-only); returns base64 image bytes in structured output.
Download a sent or received fax file. Side effects: none (read-only); returns base64 file bytes in structured output.
Download a single page from a fax file (TIFF). Side effects: none (read-only); returns base64 TIFF page in structured output.
Get a corporate member's role and faxing quota. Side effects: none (read-only).
Get information about a specific fax number. Side effects: none (read-only).
Get details of a fax scheduled for sending (outbox). wait_seconds is optional (default 0). After send-fax-uploaded, pass wait_seconds=30 on the first check so the record can become visible; omit it or pass 0 for later polls. Immediate 4xx without that wait is expected, not a lost job. Summarize for the user in plain language; do not expose raw API fields unless needed for support. Side effects: none (read-only).
Get the plan type and admin/owner flags for a user. Side effects: none (read-only).
Get metadata about the current access token (type, scopes, expiration, etc.). Side effects: none (read-only).
Get account information for a user. Side effects: none (read-only).
List webhooks currently registered for a given webhook event type. If event is omitted, returns webhooks for all supported events. Side effects: none (read-only).
Invite people to your corporate Fax.Plus account by email (max 10 per call). Pass emails as an array, e.g. ["user@example.com"]. If an address is already on Fax.Plus, the API returns a conflict — use resend-invitations for pending invites that have not joined yet. Manual invites are for orgs that do not provision users via SCIM/SAML; identity-provider-managed orgs should invite from the IdP instead. Side effects: sends invitation emails.
List areas (regions) where numbers can be purchased for a given country. Side effects: none (read-only).
List contact groups (Fax.Plus tags) with optional pagination and filters. Side effects: none (read-only).
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).
List countries where you can purchase fax numbers. is_available=false means the country is not enabled for purchase via the API - not that numbers are out of stock. Do not tell the user "no numbers in stock"; say purchase is not available for that country, or list countries with is_available=true. Side effects: none (read-only).
List fax records for a user. Returns paginated results. Summarize for the user in plain language (sent/failed, pages); do not dump raw API metadata. Side effects: none (read-only).
List all corporate members in your account. Side effects: none (read-only).
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).
List faxes in the outbox that are waiting to be sent. Translate statuses for the user (submitted/converting → preparing; scheduled_for_sending/sending → sending). Do not dump raw status timelines or internals. Side effects: none (read-only).
Search for purchasable fax numbers in a specific country and area (calling) code. Side effects: none (read-only).
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).
Purchase a Fax.Plus number by item ID. This has billing impact and requires explicit confirmation. Side effects: charges account and purchases number.
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. Do not call await-fax-upload (removed). Do not call upload-file for chat (automation-only). 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, tell the user the fax was submitted; then get-fax or get-outbox-fax with wait_seconds=30 on the first check. Side effects: mints a short-lived widget access token; opens the upload UI when the client supports MCP Apps.
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.
Resend pending corporate member invitations by email (max 10 per call). Only works for addresses that were invited but have not joined yet. Pass emails as an array, e.g. ["pending@example.com"]. Side effects: sends invitation emails.
Remove a corporate member's assignment to a fax number (DELETE assigned_to entry). user_id is the member to REMOVE from the number — NOT the owner and NOT 'who is calling'. To unassign Dom User, pass Dom User's user ID. Using self removes YOUR own assignment (common mistake). Does not cancel the number, delete it, or change owner_id. Number cannot be revoked from the admin/owner in some cases. Side effects: removes the named member from the number's assigned_to list (does not cancel the number).
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 (automation). 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. Tell the user the fax was submitted. If you check status, call get-fax or get-outbox-fax with the returned id and optional wait_seconds=30 on that first check (omit wait_seconds later). Do not narrate tool names or HTTP details to the user. Side effects: queues outbound fax for delivery.
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.
Share selected personal contact groups (tags) with corporate members in your organization. Side effects: shares contact groups to corporate scope.
Share selected personal contacts with corporate members in your organization. Side effects: shares contacts to corporate scope.
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.
Update a contact group (Fax.Plus tag). Side effects: modifies contact group.
Update a fax record's read state and/or comment. Side effects: modifies fax record metadata.
Update a corporate member's role and/or monthly fax quota. Side effects: modifies member role/quota.
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. To remove a member's assignment, use revoke-number with that member's user_id — do not use revoke-number with self unless you intend to remove your own assignment. Side effects: adds a member to the number's assigned_to list.
Update a queued outbox fax (comment only). Side effects: modifies outbox record metadata.
Update account profile/settings for a user (usually 'self'). Side effects: modifies user profile/settings.
Automation-only: upload document bytes as base64 for non-chat integrations, then call send-fax-uploaded with the returned path. NEVER use this in chat — call pipeline_start, list-numbers, list-contacts, then request-file-from-user (UI or curl). File bytes must not pass through the model for chat flows. Never expect a document as a chat attachment. Side effects: stores file for fax delivery.
よくある質問
Fax.Plus の MCP サーバーにはどう接続しますか?
エンドポイント https://mcp.fax.plus/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。
Fax.Plus の MCP サーバーは認証が必要ですか?
はい。Fax.Plus は OAuth を使用します。初回接続時に MCP クライアントがブラウザを開いてサインイン・認可を行い、以降はその認証情報を再利用します。
Fax.Plus の MCP サーバーはどのトランスポートを使用しますか?
Fax.Plus は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。
他のリモート MCP サーバー
AI Video MCP by AITuber
AI Video MCP by AITuber is a hosted MCP server that lets AI agents create and publish video. You connect it once, then ask your agent for a video in plain language. It writes the script, picks a voice, generates the visu
AdWhispr
Research competitors' winning ads, clone them for your brand and launch paused campaigns on Meta, Google and TikTok from chat.
3
3GPP Scout
Hosted 3GPP MCP server: cited search across Rel-15 through Rel-20 TS/TR specs, recent TDocs, company proposals and meeting decisions. OAuth 2.1; no local index required.
API Direct
Search and read public data from X/Twitter, Reddit, YouTube, Instagram, TikTok, Facebook, Threads, Bluesky, Trustpilot, Amazon, Google Maps, news, forums and the web. 90+ read-only tools plus ready-made research playbook
Aard
Aard connects Macroeconomic and other official data from 170+ publishers including World Bank, IMF, BIS, ECB, Eurostat, and National Statistical Offices. Aard is powered by a large graph of the metadata universe and an
コメント