# CloudSign Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## CloudSign

Create, send and track CloudSign e-signature documents and their recipients

- Record: https://musedirectory.ai/connector/cloudsign
- Category: Legal
- Developer: usefulapi (https://usefulapi.io/cloudsign/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 230ms, checked 2026-11-08T01:45:45Z
- Endpoint: https://cloudsign.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-07T22:06:41Z)
- Source: Found in the official MCP Registry (io.usefulapi/cloudsign) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fcloudsign

Connects to CloudSign, an e-signature service, through the usefulapi gateway. Muse can create signature requests, attach files, list recipients and check whether a document has been signed.

Example request: "Send the vendor agreement to both signers in CloudSign and tell me when everyone has signed."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use CloudSign to help me. It is a free service with an MCP server at https://cloudsign.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- cloudsign_list_documents: List the team's documents with their status: 0 draft, 1 waiting for recipients, 2 concluded, 3 cancelled or declined, 4 template. Paged, 100 per page. GET /documents.
- cloudsign_get_document: Get one document with its status, files and participants. GET /documents/{documentID}.
- cloudsign_list_cabinets: List the cabinets (folders) of the team. GET /cabinets.
- cloudsign_create_document: Create a new draft document. Then add files and participants, and send it with cloudsign_send_document. POST /documents.
- cloudsign_update_document: Change the title, note, message or transfer setting of a document. PUT /documents/{documentID}.
- cloudsign_add_participant: Add a recipient to a document. Wait 2-10 seconds before the next call on the same document. POST /documents/{documentID}/participants.
- cloudsign_add_file: Upload a file (usually PDF) to a document. Send the file bytes base64-encoded in content_base64, up to about 10 MB. Wait 2-10 seconds before the next call on the same document. POST /documents/{documentID}/files.
- cloudsign_send_document: Send a draft document to its recipients, or send a reminder for a document that was already sent. Recipients get an email at once, and this cannot be undone. POST /documents/{documentID}.
- cloudsign_delete_draft: Delete a draft document. Only drafts can be deleted; sent documents cannot. DELETE /documents/{documentID}.

Screening checks:
- MCP handshake: pass (Answered in 134ms)
- Domain against threat feeds (Cloudflare security DNS): pass (cloudsign.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: n/a (Tools are behind sign-in)
- Inputs asking for passwords, card numbers or seed phrases: n/a (Tools are behind sign-in)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)