SignWell
@Bidsketch
Model Context Protocol server that orchestrates SignWell's e-signature workflows — create, send, track, and manage documents and templates.
Overview
What is SignWell?
A Model Context Protocol (MCP) server that orchestrates SignWell's e-signature workflows via a standardized interface. It integrates directly with SignWell’s API to create, send, and manage documents programmatically from any MCP‑compatible client.
How to use SignWell?
Install dependencies (npm install), build the bundle (npm run build), then run the interactive setup wizard (node build/index.js setup) to store your API key and automatically configure MCP clients (Claude Desktop, Claude Code, Cursor, OpenCode). Alternatively, export the SIGNWELL_API_KEY environment variable manually and start the server with npm start. The server communicates over STDIO.
Key features of SignWell
- Interactive setup wizard for four MCP clients.
- Automatically keeps documents as drafts until explicitly sent.
- Attaches files via URL, base64, or MCP resource URI.
- Provides read‑only resources (
document://,template://). - In‑memory file storage with a 60‑minute TTL.
- No telemetry or analytics collection.
Use cases of SignWell
- Create a draft agreement, send it for signing, and check completion status.
- Retrieve a completed, signed PDF from a document ID.
- Build a custom automation that attaches files from an MCP client (e.g., Claude Desktop) to a SignWell envelope.
- Integrate e‑signature workflows into MCP‑powered assistants or IDEs.
FAQ from SignWell
What runtime does SignWell require?
Node.js v18 or newer.
How is the SignWell API key stored?
Your API key is saved locally in a platform‑specific secure directory (e.g., ~/.config/signwell-mcp/env) with 0600 permissions.
Does the server collect any usage data?
No. The server does not collect, transmit, or store any personal data, usage analytics, or telemetry.
How long are uploaded files kept in memory?
Files are stored temporarily in memory with a 60‑minute TTL and are cleared on server restart.
Can I override the default API endpoint?
Yes, set the SIGNWELL_API_BASE_URL environment variable to point to a non‑production endpoint.
