RELATED 01
OneSignal MCP Server
OFFICIAL SERVEROneSignal's hosted MCP endpoint for push, email and SMS messaging, users, segments and exports
40popularity score
Docusign MCP Server
Docusign's hosted MCP endpoint for sending envelopes, using templates and querying agreements
Official · docusign.com Remote (hosted) · Streamable HTTP ProductivityCRM and sales
Connect your client
Remote (hosted)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Its sign-in lets no client register itself: a client signs in only with an app (a client ID) registered with its maker first, so these snippets work only after that step.
Claude (desktop and web)Settings → Connectors → Add custom connector (with Client ID and Secret)
https://mcp-d.docusign.com/mcpWhat it does
The Docusign MCP Server is a remote endpoint run by Docusign that connects an MCP client to a Docusign account. Once connected, the assistant can send documents for signature from a template, check the status of envelopes already sent, start Workflow Builder workflows, and query agreements held in Agreement Manager, such as which contracts are sent but unsigned or whether an NDA with a given company is in force.
There is nothing to install. Docusign runs two endpoints: https://mcp-d.docusign.com/mcp for developer (demo) accounts and https://mcp.docusign.com/mcp for production accounts. Both answer with OAuth protected-resource metadata naming the same scopes: signature, aow_manage, spring_read, spring_write, adm_store_unified_repo_read and cors. The developer endpoint's authorization server metadata lists account-d.docusign.com for sign-in and has no dynamic client registration endpoint. A client therefore cannot register itself: for the developer endpoint you create an Integration Key and Secret Key in Docusign's Apps and Keys page and enter them in the client as the OAuth client ID and secret.
For production accounts, Docusign points Claude users to its listed Docusign connector in Claude's connector directory instead of a custom connector. Docusign's blog describes the server as generally available, and says new tools reach developer accounts before production.
What it needs
A Docusign account: a free developer account works with the developer endpoint, and a paid production account is used through the official connector. For a custom connector you need an Integration Key with a Secret Key, plus the client's OAuth callback URLs added as redirect URIs (for Claude: https://claude.ai/api/mcp/auth_callback and https://claude.com/api/mcp/auth_callback). An MCP client that supports remote servers with OAuth, such as Claude web or Desktop. A free Claude plan allows only one custom connector.
Limits
Docusign's guide says that not every IAM tool is available in every environment, and that new tools arrive on developer accounts first. What the assistant can see depends on the OAuth scopes granted and the signed-in user's Docusign permissions. The guide also warns that latency may get in the way of real-time automation, and that answers can vary with the AI model even when the data is the same. The developer endpoint does not offer dynamic client registration, so clients that rely on it cannot connect without a client ID and secret.
Who it suits
It suits teams that already use Docusign and want an assistant to send envelopes from templates, follow up on unsigned documents or ask questions across their agreements, without running any code locally. Because it is Docusign's own service, it works within the account's existing permissions and audit policies. Developers testing it need the extra Integration Key setup, and production users on Claude should add the official connector. If you want a server you can run and inspect yourself, look for a self-hosted Docusign MCP server instead, because this one is hosted only.