SignWell

Name: SignWell
Author: Bidsketch

@Bidsketch

About SignWell

Model Context Protocol server that orchestrates SignWell's e-signature workflows — create, send, track, and manage documents and templates.

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "signwell": {
      "command": "npx",
      "args": [
        "-y",
        "@signwell/mcp"
      ],
      "env": {
        "SIGNWELL_API_KEY": "your_api_key"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

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.