Is this an official Legalesign MCP server?

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

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 Legalesign?

Only when you ask, and only what it has been granted: send a Legalesign PDF template to named signers for e-signature; send a Legalesign signer a reminder email; reset a forwarded Legalesign signing back to the earlier signer; void a Legalesign document (status removed, archived). 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.

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.

MCP server · Documents and wikis

Legalesign MCP server

Legalesign in any MCP client, through Memtro: Legalesign does not publish this server. Memtro's Legalesign connector reads Legalesign 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

Legalesign e-signature: documents sent for signature with their status and each signer's progress, teams (groups), and text and PDF templates; can send a PDF template to named signers, remind a signer, reset a forwarded signer and void a document.

Reads

legalesign_list_groupsTeams (Legalesign calls them groups) this key can see, with their ids.
legalesign_list_documentsDocuments sent for signature in one team, newest as Legalesign returns them: name, status (created, fields completed, signed, removed, rejected)…
legalesign_get_documentOne Legalesign document by id: status, signers and their progress, when it was signed, tags and template.
legalesign_list_templatesTemplates in a team, text (HTML) or PDF: title, id, how many signers they take, whether they have fields, and created and modified times.

Acts, when you ask

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

legalesign_send_documentCreates a Legalesign signing document from an uploaded PDF template and sends it to the named signers.
legalesign_send_signer_reminderEmails a Legalesign signer a reminder to sign, with an optional message.
legalesign_reset_signerReverts a forwarded Legalesign signing back to the earlier signer, withdrawing the current signer's access.
legalesign_void_documentVoids a Legalesign document: it is set to removed (status 40) and archived, and can no longer be signed.

Connect it

First connect Legalesign on Dashboard → Connections, then add Memtro to your client once. The Legalesign 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 Legalesign 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 services agreement been signed yet?
› Which documents in the Sales team are still waiting on a signer?
› Who has opened the Brightwave Ltd NDA but not signed it?
› Remind the second signer on the BigCo order form to sign it today
› Send the mutual NDA template to Dan Fletcher at Globex for signature

Questions

Is this an official Legalesign MCP server?: No. It is Memtro's MCP server with Memtro's Legalesign connector behind it: the connector reads Legalesign through its API with the credentials you connect on Dashboard → Connections, and Legalesign 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 Legalesign?: Only when you ask, and only what it has been granted: send a Legalesign PDF template to named signers for e-signature; send a Legalesign signer a reminder email; reset a forwarded Legalesign signing back to the earlier signer; void a Legalesign document (status removed, archived). 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.