DocuSeal logoMCP server · Documents and wikis

DocuSeal MCP server

DocuSeal in any MCP client, through Memtro: DocuSeal does not publish this server. Memtro's DocuSeal connector reads DocuSeal through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

DocuSeal document signing: submissions with their status and each signer's progress, signers across submissions (with when they completed), and templates with their roles and fields. Can create a signature request (with emails off) or send one to its signers, re-send a signer's email, create a request or a template from HTML, change or archive a submission, change a signer's details (nobody is emailed), and rename, clone, merge, change the documents of or archive a template.

Reads

  • docuseal_list_submissionsDocuSeal submissions (documents sent for signature): template, status (pending, completed, declined, expired), dates, and each signer's role…
  • docuseal_get_submissionOne DocuSeal submission by id, with its signers' progress, the event history (sent, opened, completed, declined, with times) and document names.
  • docuseal_list_submittersDocuSeal signers across submissions: name, email, role, status (awaiting, sent, opened, completed, declined) and times.
  • docuseal_list_templatesDocuSeal templates: name, folder, author, dates, the signer roles and how many fields.
  • docuseal_get_templateOne DocuSeal template by id: roles, each field's name, type and whether required, and its documents.

Acts, when you ask

These change something in DocuSeal. 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.

  • docuseal_create_submissionCreate a DocuSeal signature request (submission) from a template for the given signers.
  • docuseal_update_submissionRename a DocuSeal submission, change or remove its expiry (null), or archive or unarchive it.
  • docuseal_archive_submissionArchive a DocuSeal submission.
  • docuseal_update_submitterChange a DocuSeal signer's name, email or external id.
  • docuseal_update_templateRename a DocuSeal template, move it to a folder (by folder name), change its external id, or replace its list of signer role names.
  • docuseal_archive_templateArchive a DocuSeal template.
  • docuseal_clone_templateCopy a DocuSeal template into a new one, optionally with a new name and folder.
  • docuseal_send_submissionSEND a DocuSeal signature request from a template: creates the submission and emails each signer…
  • docuseal_resend_submitter_emailEMAIL one DocuSeal signer their signature request again (a reminder), optionally with a new subject and body.
  • docuseal_send_to_emailsSEND a single-signer DocuSeal template for signature to each of up to 20 email addresses: one submission per address…
  • docuseal_create_submission_from_htmlCreate a one-off DocuSeal signature request from HTML documents with DocuSeal field tags…
  • docuseal_create_template_from_htmlCreate a DocuSeal template from HTML with field tags.
  • docuseal_merge_templatesMerge 2 to 10 DocuSeal templates into one new template; the originals are kept.
  • docuseal_update_template_documentsChange a DocuSeal template's documents from HTML: add a document, replace the one at a position (its fields carry over)…

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

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

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

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

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

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

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

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 DocuSeal 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 Acme signed the NDA yet?
  • › Which submissions are still waiting for signature?
  • › Who signed anything this week?
  • › Send the contractor agreement to jo.baker@northwind.example for signature
  • › Remind the Acme signer about the NDA

Questions

Is this an official DocuSeal MCP server?
No. It is Memtro's MCP server with Memtro's DocuSeal connector behind it: the connector reads DocuSeal through its API with the credentials you connect on Dashboard → Connections, and DocuSeal 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 DocuSeal?
Only when you ask, and only what it has been granted: create a signature request from a template without emailing anyone (each completed document is billed on Cloud Pro); rename a submission, change its expiry, or unarchive it; archive a submission (it can no longer be signed, and is not deleted); change a signer's name, email or external id (nobody is emailed); rename a template, move it to a folder, or change its roles; archive a template; clone a template; send a signature request from a template, emailing each signer their link; re-send a signer their signature request email; send a template for signature to a list of email addresses; create a signature request from HTML (sent only when asked); create a template from HTML; merge templates into a new one; add, replace or remove a template's documents from HTML. 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

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time