Where it fits
Legal and sales operations staff tracking contract envelopes and signing status through an assistant.
- Check the signing status of an outstanding envelope
- Find the vendor agreement sent last week
- Nudge the next signer in a signature workflow
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Docusign
These skills cover adjacent tasks, matched by purpose and the work each one describes.
A lightweight way for small businesses without lawyers on staff to review NDAs, MSAs, and vendor contracts. Contracts arrive from local files, mail attachments in Gmail or M365, a connected store such as Google Drive or M365, or DocuSign envelopes. The skill points out non-standard terms, spells out the risks in plain language, and returns a redline marked up in its own DOCX. It suits a request to review a contract, a question about what is being signed, red flags or concerns, a payment-terms check, or a contract or legal agreement the user uploads or forwards.
Answers questions across a corpus of contract documents with verified citations. It handles questions about what a contract says, which contracts contain a clause, what changed between amendments, and other questions that require reading and citing across contract files. The corpus must be on the local filesystem.
Extracts plain text from document files in PDF, DOCX, XLSX, PPTX, RTF, and plain text, markdown, or HTML formats. It fits cases where a binary document needs to become text, such as a contract PDF or an EHR DocumentReference attachment. Other skills, including fhir, call scripts/extract.ts directly, while the contracts MCP server bundles its own copy at servers/documents/src/extract.mjs, so fixes must be ported to both.
No skills found
Try a different search term or clear the filters.
Install it in your client
Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.
- 01
Run this command in your terminal
This adds Docusign as a remote Streamable HTTP server in Claude Code.
Claude Codeclaude mcp add --transport http docusign https://mcp.docusign.com/mcp --scope project - 02
Verify the connection
Run claude mcp list, or open /mcp in a Claude Code session.
Learn more about MCP in Claude Code
- 01
Run this command in your terminal
This adds Docusign as a remote Streamable HTTP server in Codex.
Codex# Add this to Codex MCP settings: [mcp_servers."docusign"] url = "https://mcp.docusign.com/mcp" - 02
Verify the connection
Run codex mcp list, or open /mcp in a Codex session.
Learn more about MCP in Codex
- 01
Install with one click
This opens Cursor with the server pre-filled. Review the connection before accepting it.
Install in Cursor - 02
Verify the connection
Open Cursor's MCP settings and enable the server if it is not active.
Learn more about MCP in Cursor
- 01
Install with one click
This opens VS Code with the server pre-filled. Review the connection before accepting it.
Install in VS Code - 02
Verify the connection
Run MCP: List Servers from the Command Palette and start the server.
Learn more about MCP in VS Code
More clients, including project and global config files, are in the sidebar.
Endpoint and configuration
The installer uses the server name docusign. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
docusignappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Check the signing status of an outstanding envelope. Check the result before you give the server more access.
- 3Check permissions.
Confirm the provider's credential model before relying on scopes or key permissions. Remove the server and revoke any token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Docusign documentationhttps://claude.com/connectors/docusign