
Docusign Navigator
co.thisdot.docusign-navigatorPublished by docusign-navigator.thisdot.coOfficial publisherv1.4.0Updated Oct 24, 2026
Secure Docusign Navigator integration for AI assistants to access and analyze agreement data.
Overview
Connects an AI assistant to Docusign Navigator so it can list, search and analyze your agreements in natural language.
- What you can do
- This remote MCP server links an AI assistant to Docusign Navigator. It lets the assistant check authentication status, list all agreements, retrieve details for a specific agreement by ID, and search agreements by name, counterparty or status such as pending signature or expired. Results come from a live connection to the user's Docusign account.
- When to use it
- Useful when you work with contracts in Docusign and want to ask questions like which agreements are pending signature or what contracts exist with a given company, without opening the Docusign interface or writing API calls. It suits users who already have Navigator access and a compatible MCP client.
- Requirements
- A remote MCP endpoint at an active Docusign account with Navigator access, a compatible MCP client that supports HTTP transport, and an internet connection. No API keys or environment variables are declared; authentication happens through an OAuth 2.0 sign-in prompt on first use.
Installation
In SourceWeft
- Open Docusign Navigator in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.thisdot.docusign-navigator%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"docusign-navigator": {
"type": "http",
"url": "https://docusign-navigator.thisdot.co/mcp"
}
}
}README
Docusign Navigator MCP Server (Deprecated)
[!WARNING] This project is no longer maintained and has been archived. The hosted server at
https://docusign-navigator.thisdot.co/mcpis being shut down.
Use the official Docusign MCP Server instead
Docusign now provides an official MCP server with support for agreements, envelopes, workflows, and more:
Source: README.md at commit 209fabd
Tools
0Version history
2- v1.4.0LatestOct 19, 2026
- v1.3.0Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts