Docusign Navigator MCP Server

What Docusign Navigator MCP Server MCP server does

Docusign Navigator MCP Server connects an AI assistant to a user’s Docusign Navigator account. It exposes agreement information through MCP so users can ask natural-language questions instead of manually searching Navigator or building direct API requests.

The available capabilities cover four main tasks: checking whether the Docusign connection is authenticated, listing agreements, retrieving information for a specific agreement, and searching agreements. Example searches include finding contracts associated with a company, locating service agreements, or identifying agreements that have expired or are pending signature.

How it works

The project provides a hosted MCP endpoint at https://docusign-navigator.thisdot.co/mcp. An MCP client connects to that endpoint over HTTP. When the assistant first needs to use a Docusign command, the user receives an authorization link, signs in to Docusign, and approves access. After authorization, the assistant can issue requests against the connected Navigator account.

Docusign Navigator MCP Server uses OAuth 2.0 for authentication. The README states that agreement data is not stored on the service and that access is made directly to the Docusign account. Users can revoke the connection through Docusign settings.

Setup and configuration

A Docusign account with Navigator access is required, along with an MCP-compatible AI client and an internet connection. The hosted endpoint can be added to Claude Desktop with mcp-server-fetch and the endpoint URL. In Visual Studio Code, use the MCP server command, choose the HTTP or Server-Sent Events option, and enter the same URL.

Other MCP clients can use an HTTP server entry with the endpoint URL and an http type. After adding the server, complete the OAuth authorization flow when prompted. No environment variables or local service deployment settings are specified in the provided material.

Tools and capabilities

The assistant can use the Docusign Navigator MCP Server to:

• Check Docusign authentication status.
• List the user’s agreements or documents.
• Retrieve details for an agreement by ID.
• Search agreements using terms such as a company name or agreement type.
• Find agreements based on states such as pending signature or expired.

These functions are intended for reading and analyzing agreement data. The provided material does not describe tools for creating, editing, sending, signing, or deleting agreements.

Limitations and notes

The account must have Docusign Navigator enabled and contain agreements available to the authenticated user. The AI client must support MCP HTTP transport. If no agreements appear, the documented checks are to confirm Navigator access, verify that agreements exist in Navigator, and authenticate again.

The repository describes a hosted deployment rather than detailed instructions for running a private instance. It points contributors to a separate contributing guide for development, architecture, and deployment information. The provided material does not specify a software license or configurable environment variables.