Is this an official DocuSign MCP server?

No. It is Memtro's MCP server with Memtro's DocuSign connector behind it: the connector reads DocuSign through its API with the credentials you connect on Dashboard → Connections, and DocuSign 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 DocuSign?

Not yet. Today every DocuSign tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

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 · CRM and sales

DocuSign MCP server

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

Agreements sent for signature: envelopes with their signers, status, documents list, custom fields and audit trail, plus templates and account users. Read-only; document content is not fetched.

Reads

docusign_envelopesFind DocuSign envelopes (agreements sent for signature) changed in a date window, optionally by status, free text (subject…
docusign_envelopeOne envelope in full: subject, status and dates, every recipient with status and signed/declined times, the documents list (names and page counts…
docusign_templatesTemplates in the account (reusable agreement set-ups): name, description, owner, folder, created/modified/last-used dates.
docusign_usersUsers (members) of the DocuSign account with status, type, admin flag and permission profile.

Connect it

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

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer 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-..."
      }
    }
  }
}

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 DocuSign 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

› Which contracts are still waiting for a signature from Acme?
› Did the Northwind MSA get signed last week, and by whom?
› Why was the renewal agreement declined?
› Show me the audit trail for the envelope sent to jane@acme.com

Questions

Is this an official DocuSign MCP server?: No. It is Memtro's MCP server with Memtro's DocuSign connector behind it: the connector reads DocuSign through its API with the credentials you connect on Dashboard → Connections, and DocuSign 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 DocuSign?: Not yet. Today every DocuSign tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
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.