SignWell MCP Server

The SignWell MCP server is the official Model Context Protocol integration for SignWell, an electronic signature platform for legally binding signatures. It lets MCP-compatible AI assistants (Claude Desktop, Claude Code, Cursor, and others) create draft documents, send them for signature, track signing status, download the completed PDFs, and instantiate documents from reusable templates, all from within a chat session.

The server is published as the @signwell/mcp npm package and is maintained in the Bidsketch/signwell-mcp GitHub repository (Bidsketch is SignWell's parent company). It exposes a small, focused tool surface centered on the document lifecycle, plus read-only MCP resources (document://{id} and template://{id}) for inspecting documents and templates as JSON. Documents default to draft status as a safety measure, requiring an explicit send action before signature requests are dispatched.

Setup includes an interactive wizard (npx @signwell/mcp setup) that writes credentials with secure file permissions and auto-configures supported MCP clients, or you can configure it manually using the SIGNWELL_API_KEY environment variable. The server supports common office and image file types up to 25 MB, text-tag based field placement, sequential signing, CC recipients, and signing reminders.

Tools

Prerequisites

• A paid SignWell account with API access enabled
• A SignWell API key from Settings > API in the SignWell dashboard
• Node.js v18 or newer
• An MCP-compatible client (Claude Desktop, Claude Code, Cursor, etc.)

Option A: Interactive setup wizard (recommended)

Run the official setup command in a terminal. It will prompt for your API key, store credentials securely, and auto-configure your MCP client:

npx @signwell/mcp setup

Preview the changes without writing files:

npx @signwell/mcp setup --print

Restart your AI client after setup completes.

Option B: Manual Claude Desktop config

Add the following to your claude_desktop_config.json under mcpServers:

{
  "mcpServers": {
    "signwell": {
      "command": "npx",
      "args": ["@signwell/mcp"],
      "env": {
        "SIGNWELL_API_KEY": "your-api-key-here"
      }
    }
  }
}

Environment variables

• SIGNWELL_API_KEY (required): your SignWell API key
• SIGNWELL_API_BASE_URL (optional): defaults to https://www.signwell.com/api/v1
• SIGNWELL_API_TIMEOUT_MS (optional): defaults to 90000

Credential storage paths (set by the wizard)

• macOS: ~/Library/Application Support/SignWell/MCP/env
• Linux: ~/.config/signwell-mcp/env
• Windows: %APPDATA%/SignWell/MCP/env

• Draft an NDA or contract inside Claude, attach a PDF, and send it to a counterparty for signature without leaving the chat
• Generate a customer order form from a saved SignWell template, populate signer fields, and dispatch it in one step
• Check the live status of outstanding signature requests ("who hasn't signed the MSA yet?") and trigger a reminder for stalled signers
• Download the executed, audit-trailed PDF of a completed contract directly into a project folder for archival
• Bulk-send templated agreements (e.g. vendor agreements, employment letters) by iterating an MCP-enabled agent over a list of recipients

• "Create a draft SignWell document from contract.pdf with John (john@acme.com) and Sarah (sarah@acme.com) as sequential signers, but do not send it yet."
• "Use my 'Vendor NDA' template to generate a document for legal@example.com and send it."
• "What's the current signing status of SignWell document doc_abc123? Who still needs to sign?"
• "Send a reminder for any SignWell documents in my account that have been pending more than 5 days."
• "Download the completed signed PDF for the Acme Corp MSA and save it to the project folder."

• Official server maintained by SignWell (Bidsketch), so the integration tracks the SignWell API directly
• Focused, well-scoped tool surface covering the full document lifecycle: create, send, track, download, and template instantiation
• Draft-safe by default: documents must be explicitly sent, reducing accidental dispatches by an LLM
• Interactive setup wizard auto-configures Claude Desktop, Cursor, and other clients with secure credential storage

• Requires a paid SignWell plan with API access; the free tier will not work
• Small tool set: no first-class tools for managing webhooks, bulk sends, or account-level admin operations (those require the REST API directly)
• Requires Node.js v18+ locally to run the npx command (no hosted remote endpoint from SignWell itself)

• DocuSign MCP integrations via Pipedream, Zapier, or Composio for teams already on DocuSign
• Dropbox Sign (HelloSign) via Composio or Zapier MCP for an alternative e-signature provider
• Pipedream SignWell MCP (https://mcp.pipedream.net/v2) as a hosted alternative if you prefer not to run Node.js locally