# signforge [Health: Active]

**Category:** 🤝 Agreements & Coordination  
**Repository:** https://github.com/kumarprobeops/signforge-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 138  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/signforge

## Description
Send documents for e-signature from AI agents. Upload, sign, and download PDFs.

## Tools
Capabilities this server exposes over MCP:

- **create_and_send** — Create an envelope with a PDF document, add a signer, and send it for e-signature. Returns the envelope ID and a signing URL. Provide either a local file path (pdf_path) or base64-encoded PDF content (pdf_base64).
- **check_status** — Check the current status of an envelope. Returns the envelope details including recipient signing status, document availability, and timestamps.
- **download_signed** — Download the signed PDF document for a completed envelope. The envelope must be in 'completed' status. Saves the file to the specified output path.
- **list_envelopes** — List your envelopes with optional filtering by status. Returns envelope summaries including titles, statuses, and recipient information.
- **send_envelope** — Send a draft envelope for signing. The envelope must be in 'draft' status with at least one recipient and one field configured.
- **void_envelope** — Void (cancel) an active envelope. The envelope must be in 'sent' status. All pending signatures will be cancelled and signers will be notified.
- **delete_envelope** — Permanently delete an envelope. Only draft and voided envelopes can be deleted.
- **download_certificate** — Download the audit certificate PDF for a completed envelope. The certificate contains the full audit trail with timestamps and IP addresses.
- **download_archive** — Download a ZIP archive containing the signed PDF, audit certificate, and all related documents for a completed envelope.
- **get_embed_url** — Generate an embeddable signing URL for an envelope. This URL can be embedded in an iframe for in-app signing experiences.
- **create_webhook** — Create a webhook to receive real-time notifications for envelope events. Events include: envelope.sent, envelope.viewed, envelope.signed, envelope.completed, envelope.expired, envelope.voided, envelope.declined.
- **list_webhooks** — List all configured webhooks for your account.
- **delete_webhook** — Delete a webhook by its ID. The webhook will stop receiving events immediately.
- **list_templates** — List your reusable document templates. Templates contain pre-placed fields and can be used to quickly create envelopes.
- **create_from_template** — Create an envelope from a template. Optionally pre-fill field values and send immediately. The template's fields will be mapped to the provided recipients.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "signforge": {
    "command": "npx",
    "args": ["-y","@signforge/mcp-server"],
    "env": {
      "SIGNFORGE_API_KEY": "",
      "SIGNFORGE_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `SIGNFORGE_API_KEY`, `SIGNFORGE_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/signforge/readme_