DottedSign

What DottedSign MCP server does

DottedSign MCP server exposes DottedSign eSignature workflows to compatible AI assistants. After authorization, you can ask an assistant to find signing tasks, inspect document content and incomplete fields, browse saved templates, create a task from a template, organize signer order, send a task, or void an existing task.

The integration is intended for teams that regularly handle contracts, employment documents, agreements, and other signing workflows. It can also help explain an agreement before signing by summarizing its contents and identifying fields that still need attention. Recipients continue to use the regular DottedSign email link; they do not need an AI tool or a DottedSign account.

How it works

Requests are expressed in natural language through Claude, ChatGPT, or Claude Code. The assistant translates the request into one or more DottedSign operations and returns the result in the conversation. Examples include listing pending tasks, checking the status of a document, creating a task from an Employment Contract template, or canceling a task by name.

Authorization is completed through DottedSign’s OAuth flow. Access can be revoked from DottedSign, and the connector can also be removed from the assistant’s settings. If a user has already created a signature in DottedSign, the assistant can sign documents on that user’s behalf in addition to preparing, sending, and tracking tasks.

Setup and configuration

The hosted MCP endpoint is:

https://mcp.dottedsign.com/dottedsign-api/mcp

For Claude Desktop or Claude’s web interface, add the URL under Settings, Connectors, and Add Connector, then complete the DottedSign sign-in flow. Claude Code can register the same endpoint with:

claude mcp add --transport http dottedsign https://mcp.dottedsign.com/dottedsign-api/mcp

ChatGPT uses the connector settings to add the same URL and authorize DottedSign. A DottedSign account is required. Claude works with a free account, while ChatGPT may require a paid plan. DottedSign plan limits still apply: sending tasks and some template-based workflows require an eligible paid plan.

For reliable task creation, provide the signer’s name and email and use the template’s exact name. FieldSearchKey keywords can help map external data to matching template fields.

Tools and capabilities

The documented operations include:

• Listing and filtering signing tasks.
• Reading a task’s content and fields.
• Retrieving saved templates.
• Creating a task from a template.
• Setting the order in which people sign.
• Sending a signing task to recipients.
• Voiding or canceling a task.
• Summarizing agreements and identifying fields to complete.

The exact tool set is controlled by the hosted MCP server and may change over time.

Limitations and notes

Free and Pro DottedSign plans have feature restrictions. In particular, the Free plan cannot create document templates, and template-based sending may be unavailable; the README recommends the Business plan for the full workflow, including creation, sending, tracking, and signing.

The connector itself does not replace DottedSign authorization or plan access. If a task cannot be found, refer to the document by its DottedSign name and confirm that it exists in the account. If authorization fails, sign in to DottedSign in the same browser and retry. Remove the connector and revoke DottedSign access when disconnecting.

DottedSign MCP server is a hosted HTTP integration rather than a locally configured API-key service. The README names Claude, Claude Code, and ChatGPT as supported assistants; other MCP clients are not specifically documented here.