What it does
The server connects MCP clients to SignWell's e-signature workflows. An MCP client can send documents for e-signature, check their signing status and manage templates. Previously created documents and templates are exposed as read-only JSON snapshots, and completed PDFs can be retrieved.
It is relevant when a SignWell account is already in use and documents should be created, sent or checked from an MCP-compatible assistant or editor. The document_create and template_create_document tools always set draft: true, so documents they create start as drafts.
Setup needs Node.js v18 or newer and a SignWell API key with document access, supplied through the SIGNWELL_API_KEY environment variable. An interactive setup wizard stores credentials locally and writes configuration for Claude Desktop, Claude Code, Cursor and OpenCode, backing up each file before writing. Optional variables change the API base URL and the HTTP timeout, which defaults to 90000 ms. The server runs over stdio. The publisher states that it does not collect telemetry or share data with third parties.
Limitations and requirements
Requires a SignWell API key with document access, supplied through SIGNWELL_API_KEY. Requires Node.js v18 or newer. Files provided via file_store are held only in memory, for up to 60 minutes, and are cleared on server restart.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source
io.github.Bidsketch/signwell-mcp
Send documents for e-signature, track signing, and manage templates in SignWell from any MCP client.
v0.3.9As shown on registry.modelcontextprotocol.io when we last read it