Log inSubmit server
Signforge logo

Signforge

Connect AI agents to SignForge to send, track, manage, and download e-signature documents.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Signforge

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "signforge": {
      "command": "npx",
      "args": [
        "-y",
        "@signforge/mcp-server"
      ],
      "env": {
        "SIGNFORGE_API_KEY": "YOUR_VALUE_HERE",
        "SIGNFORGE_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 15 tools correctly (11d ago).

Overview

The signforge MCP server connects AI agents to SignForge’s e-signature API for sending and managing PDF envelopes. It supports local PDF paths or base64-encoded files, reusable templates, embedded signing URLs, document downloads, and envelope webhooks. Use it when an agent needs to start signature workflows, monitor progress, retrieve completed documents, or manage the envelope lifecycle.

Use cases

  • Send a PDF agreement to a signer
  • Track envelope completion and signing timestamps
  • Download signed documents and audit certificates
  • Create agreements from reusable templates
  • Subscribe to envelope status events

Key features

  • PDF upload from a path or base64
  • Envelope lifecycle management
  • Signed document and audit downloads
  • Template-based envelope creation
  • Embedded signing URL generation
  • Envelope webhook management

Tools15

What Signforge lets your agent do. Expand a tool for its parameters.

Verified live~1.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 47d

What it can do

From the 15 tools this server returned when we ran it.

Can delete or modify data · 2Makes network requests · 7Read-only tools · 13
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age206 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @signforge/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads138Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed15Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Signforge works

What the signforge MCP server does

The signforge MCP server exposes SignForge’s e-signature API through MCP tools. It lets an AI client upload a PDF, assign a signer, and send the document for signature. Uploads can use a local file path or a base64-encoded PDF.

Envelope tools cover the main lifecycle: listing envelopes, filtering them by status, checking signing progress, sending drafts, voiding active envelopes, and permanently deleting drafts or voided envelopes. Status information includes timestamps and available documents.

Completed signing workflows can produce several outputs. The server can save the signed PDF to a local file, download the audit certificate containing the audit trail, or download a ZIP archive containing the signed PDF, certificate, and other documents. It can also generate an embeddable signing URL for an in-app signing experience.

How it works

The MCP client starts the package with npx -y @signforge/mcp-server and passes requests to SignForge’s API. Authentication uses an API key from SignForge Developer Settings. A separate API base URL can be configured for self-hosted instances or staging environments.

Template-based workflows are supported through template listing and envelope creation. An agent can find a reusable template, provide pre-filled field values, and either send the resulting envelope immediately or retain it as a draft.

Webhook tools let an agent create, list, and delete subscriptions for envelope events. Supported events include sent, viewed, signed, completed, expired, voided, and declined. Webhook creation returns a secret that can be saved for signature verification.

Setup and configuration

Install and run the server through npx; no separate package installation is described. Set SIGNFORGE_API_KEY in the MCP client configuration or shell before starting it. The key is required and can be generated from SignForge’s Developer Settings.

SIGNFORGE_API_URL is optional and defaults to https://signforge.io/api/v1. Change it only when targeting a self-hosted or staging API. Sandbox-mode API keys create test envelopes that do not send real emails, which supports development and testing.

The documented client configurations cover Claude Desktop, Claude Code, and Cursor. After adding the configuration, restart the client so it loads the server.

Tools and capabilities

The available operations include:

  • Create and send an envelope from a PDF.
  • Check, list, send, void, and delete envelopes.
  • Download signed PDFs, audit certificates, and ZIP archives.
  • Generate embedded signing URLs.
  • List templates and create envelopes with pre-filled values.
  • Create, list, and delete envelope webhooks.

Limitations and notes

The server requires a valid SignForge API key, and API permissions must cover the requested operation. Invalid or expired keys produce authentication errors, while insufficient scopes produce permission errors. SignForge rate limits can also cause requests to return an HTTP 429 response.

The documented PDF input options are a local path and base64-encoded content. The download tools save files to local paths. Sandbox keys are intended for test envelopes and do not send real signing emails.

The signforge MCP server does not describe built-in user interfaces, custom field placement, or signer routing beyond the inputs supported by its listed tools. Consult SignForge’s API documentation for API-specific behavior and permissions.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Signforge

signforge is an MCP server that connects AI agents to SignForge’s e-signature API. Its main tools upload and send PDFs, check and manage envelopes, download signed documents and audit certificates, create envelopes from templates, generate embedded signing URLs, and manage envelope webhooks.

Run it with `npx -y @signforge/mcp-server` and provide `SIGNFORGE_API_KEY`. Add that command and environment variable to your MCP client configuration, then restart the client. The documented setup uses Claude Desktop, Claude Code, or Cursor.

It requires `SIGNFORGE_API_KEY`, obtained from SignForge Developer Settings. `SIGNFORGE_API_URL` is optional and defaults to `https://signforge.io/api/v1`; use it for self-hosted or staging instances.

Yes. It can save a completed envelope’s signed PDF, download its audit certificate, or download a ZIP archive containing the signed PDF, certificate, and all documents.

Yes. Cursor is one of the clients documented for this server. Add the server command and `SIGNFORGE_API_KEY` to Cursor’s `.cursor/mcp.json` settings, then restart Cursor.

Related MCP servers

All in Agreements & Coordination All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSignforge AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/signforge?style=directory)](https://allmcps.com/mcp/signforge)
HTML Embed
<a href="https://allmcps.com/mcp/signforge"><img src="https://allmcps.com/api/badge/signforge?style=directory" alt="Signforge on AllMCPs" /></a>