Skip to main content

MCP Server

The DocuTrust MCP (Model Context Protocol) server enables AI agents and coding assistants to manage templates, submissions, and signers programmatically. It exposes DocuTrust operations as tools that any MCP-compatible client can call.

Installation

Run the MCP server directly with npx (no installation required):
Or install globally:

Configuration

Environment Variables

Claude Code

Add the following to your Claude Code MCP configuration (.claude/mcp.json or project settings):

Claude Desktop

Add to your Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

Available Tools

The MCP server exposes tools organized into three tiers based on their impact:

Send tool gating

By default, the binding send tools (send_submission, send_reminder) are not registered in the stdio MCP server. Set the DOCUTRUST_ALLOW_SEND environment variable to enable them:
Each send tool also requires confirmed_by_user: true as a parameter, providing a human confirmation step.

list_templates

List all available templates in your account. Parameters: Example response:

get_template

Get detailed information about a specific template. Parameters: Example response:

get_audit_trail

Get account-wide compliance audit log entries. Parameters:

download_completed_document

Download a signed PDF for a completed submission. Available in stdio MCP only. Parameters:

list_submission_documents

List generated documents for a submission. Parameters:

create_draft_submission

Create a draft submission from a template. No emails are sent until the draft is explicitly sent. Parameters:

update_draft_submission

Edit a draft submission before sending. Only works on submissions with draft status. Parameters:

send_submission

Send a draft submission for signing. This is a legally binding action. Only available when DOCUTRUST_ALLOW_SEND is set (stdio MCP) or the token has submissions:send scope (remote MCP). Parameters:

create_submission

Create a new submission from a template and send it to recipients for signing. Parameters: Example response:

create_submissions_from_emails

Create multiple submissions at once from a comma-separated list of email addresses. Each email gets its own submission. Parameters: Example response:

get_submission

Get detailed information about a specific submission. Parameters: Example response:

list_submissions

List submissions with optional filtering. Parameters: Example response:

send_reminder

Send a reminder email to a submitter who has not yet completed signing. Parameters: Example response:

get_submitter

Get detailed information about a specific submitter. Parameters: Example response:

Usage Examples

Once the MCP server is connected, you can use natural language to interact with DocuTrust through your AI assistant.

List templates

“Show me all my DocuTrust templates”
The agent calls list_templates and presents the results.

Send a document for signing

“Send the Employment Agreement template to jane@example.com for signing”
The agent calls create_submission with the template ID and submitter email.

Check submission status

“What’s the status of submission 89?”
The agent calls get_submission with the submission ID and reports back.

Bulk send

“Send the NDA template to alice@example.com, bob@example.com, and carol@example.com
The agent calls create_submissions_from_emails with the template ID and email list.

Send a reminder

“Remind submitter 142 to sign their document”
The agent calls send_reminder with the submitter ID.

Remote MCP endpoint

For hosted AI agents that can’t spawn a local process, SpitShake provides a remote MCP endpoint at POST /mcp.

Authentication

Use a scoped API token or OAuth access token via Authorization: Bearer <token>.

Protocol

The endpoint speaks JSON-RPC 2.0. Supported methods: initialize, tools/list, tools/call, ping.

Scope-gated tools

Tools are only visible when the token carries the required scope. A read-only token (templates:read, submissions:read) sees 6 READ tools. Adding submissions:draft reveals the PREPARE tools. Adding submissions:send reveals the BINDING tools. The remote MCP includes all 10 tools from the stdio MCP plus write tools that use direct model operations (create/update drafts, send submissions, send reminders).

Security

  • The MCP server uses your API token for authentication. All operations are scoped to the token’s permissions.
  • The server runs locally on your machine and communicates with DocuTrust over HTTPS.
  • API tokens should be stored in environment variables, not hardcoded in configuration files that are committed to version control.
  • Use tokens with the minimum required scopes for your use case.
Never share your API token or commit it to a public repository. Use environment variables or a secrets manager to store tokens securely.