Documenso MCP server

What the model can do

Documenso document signing: documents and templates with their status and who has signed, an envelope's audit trail, and folders. Can create a document from a template (draft, or sent to its signers when asked), place or remove fields, make a draft signable (email off) or email recipients a reminder, add, change or remove recipients, record a recipient's rejection, add, change or remove link attachments, remove a file, rename, duplicate, cancel or delete a document, and create, change or delete folders.

Reads

• documenso_list_envelopesDocumenso documents (or templates) for the token's team: title, status (DRAFT, PENDING, COMPLETED, REJECTED, CANCELLED), dates, how many have signed…
• documenso_get_envelopeOne Documenso document or template by its envelope id: status, dates, the email subject, files, and every recipient with role, signing…
• documenso_envelope_audit_logThe audit trail of one Documenso envelope: what happened (sent, opened, signed, completed…), when, and by whom.
• documenso_list_foldersDocumenso folders: name, whether for documents or templates, parent and visibility.
• documenso_list_templatesDocumenso templates for the token's team: the template number documenso_use_template needs, title, folder, and each recipient slot's id and role…
• documenso_list_attachmentsThe link attachments on one Documenso document: id, label and the link.

Acts, when you ask

These change something in Documenso. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• documenso_create_folderCreate a folder in Documenso for documents or templates, optionally inside another folder.
• documenso_update_folderRename a Documenso folder, move it under another folder, or pin or unpin it.
• documenso_delete_folderDelete a Documenso folder.
• documenso_update_envelopeRename a Documenso document or template, change its external id, or move it to another folder.
• documenso_duplicate_envelopeMake a copy of a Documenso document or template, with its recipients and fields unless told otherwise.
• documenso_distribute_envelopeMove a draft Documenso document out of draft so its recipients can sign it, with email distribution forced off: nobody is emailed…
• documenso_redistribute_envelopeEmail the signing link again to recipients of a pending Documenso document who have not acted yet, renewing any expired links.
• documenso_cancel_envelopeCancel a pending Documenso document.
• documenso_delete_envelopeDelete a Documenso document or template.
• documenso_add_recipientsAdd recipients (signers, approvers, viewers, CCs) to a Documenso document.
• documenso_update_recipientChange a recipient on a Documenso document: name, email, role or signing order.
• documenso_remove_recipientRemove a recipient from a Documenso document.
• documenso_use_templateCreate a Documenso document from a template, filling each of the template's recipient slots…
• documenso_create_fieldsPlace fields (signature, initials, name, email, date, text, number) for recipients on a draft Documenso document…
• documenso_delete_fieldRemove one field from a Documenso document.
• documenso_reject_for_recipientRecord that a recipient declined to sign a pending Documenso document, on their behalf, because they said so outside Documenso.
• documenso_create_attachmentAttach a labelled https link to a Documenso document; every recipient sees it when they open the document.
• documenso_update_attachmentChange a Documenso attachment's label and link (both are sent; the old ones are replaced).
• documenso_delete_attachmentRemove a link attachment from a Documenso document.
• documenso_delete_envelope_itemRemove one file from a Documenso document that holds several (file ids from documenso_get_envelope).

Connect it

First connect Documenso on Dashboard → Connections, then add Memtro to your client once. The Documenso tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Documenso connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Has the Northwind contract been signed yet?
• › Who still has to sign the Brightwave Ltd NDA?
• › When did Dan Fletcher open the Acme order form?
• › Which documents were rejected or cancelled last month?
• › Send a reminder to everyone who has not signed the BigCo renewal

Questions

Is this an official Documenso MCP server?

No. It is Memtro's MCP server with Memtro's Documenso connector behind it: the connector reads Documenso through its API with the credentials you connect on Dashboard → Connections, and Documenso publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Documenso?

Only when you ask, and only what it has been granted: make a draft document signable without emailing anyone (links are shared from Documenso); resend the signing email to recipients who have not acted; add recipients to a document (a pending document may invite them at once); change a recipient's name, email, role or signing order; remove a recipient from a document; rename a document, change its external id or move it to a folder; duplicate a document or template; cancel a pending document (its signing links stop working); delete a document permanently; create a folder; rename, move or pin a folder; delete a folder; create a document from a template, as a draft or sent to its signers; place signature and other fields on a draft document; remove a field from a document; record that a recipient declined to sign; attach a link to a document; change an attachment's label or link; remove an attachment; remove one file from a document. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Documents and wikis

• Google Drive MCP server
• Notion MCP server
• Confluence MCP server
• SharePoint and OneDrive MCP server
• Guru MCP server
• Dropbox MCP server