Signforge

io.github.kumarprobeopsPublished by GitHub account kumarprobeopsv1.2.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow Files & Storage Business & Commerce

Server details

Identifier: io.github.kumarprobeops/signforge
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account kumarprobeops for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.kumarprobeops%2Fsignforge.svg)](https://sourceweft.com/mcp/io.github.kumarprobeops%2Fsignforge?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an AI assistant send PDFs for e-signature, track envelope status, and download signed copies and audit certificates via SignForge.

What you can do: Connects an assistant to the SignForge e-signature API. Tools cover creating and sending envelopes from a local PDF path or base64 data, listing and checking envelope status, sending drafts, voiding or deleting envelopes, and downloading signed PDFs, audit certificates, and ZIP archives. It also lists and creates envelopes from templates with pre-filled fields, generates embeddable signing URLs, and manages webhook subscriptions for envelope events.
When to use it: Useful when you want an assistant to handle routine e-signature work: sending an NDA or contract to a recipient, checking whether a document has been signed, retrieving the signed file and audit trail, or starting envelopes from standard templates. Sandbox keys let you test the flow without sending real emails.
Requirements: Runs locally over stdio, typically via npx @signforge/mcp-server, so Node.js and network access are needed. A SignForge account and API key are required, supplied as the SIGNFORGE_API_KEY environment variable. The optional SIGNFORGE_API_URL variable changes the API base URL for self-hosted or staging instances.

Before you install

The API key SIGNFORGE_API_KEY is a secret stored in the client configuration; anyone with it can act on your SignForge account. Tools send documents to recipients, void or delete envelopes, and create or delete webhooks, so actions have real external effects. Creating a webhook returns a signing secret to save for verification. Signed PDFs and audit certificates are written to local files.

Installation

In SourceWeft

Open Signforge in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@signforge/mcp-server

Send documents for e-signature directly from Claude Desktop, Claude Code, Cursor, and other AI agents — powered by SignForge, the free e-signature platform.

What It Does

This MCP server connects AI agents to SignForge's e-signature API. Your AI assistant can:

Send documents for signature — upload a PDF, specify a signer, and send in one step
Manage envelopes — send, void, delete, and check status
Download documents — signed PDFs, audit certificates, and ZIP archives
Use templates — create envelopes from reusable templates with pre-filled fields
Manage webhooks — subscribe to real-time envelope events
Generate embed URLs — create embeddable signing experiences

Quick Start

1. Get Your API Key

2. Configure Your AI Client

Choose your client below and add the configuration:

Claude Desktop

Add to your claude_desktop_config.json:

json

{  "mcpServers": {    "signforge": {      "command": "npx",      "args": ["-y", "@signforge/mcp-server"],      "env": {        "SIGNFORGE_API_KEY": "your-api-key-here"      }    }  }}

{  "mcpServers": {    "signforge": {      "command": "npx",      "args": ["-y", "@signforge/mcp-server"],      "env": {        "SIGNFORGE_API_KEY": "your-api-key-here"      }    }  }}

Config file location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Claude Code

Then set the environment variable in your shell:

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

json

{  "mcpServers": {    "signforge": {      "command": "npx",      "args": ["-y", "@signforge/mcp-server"],      "env": {        "SIGNFORGE_API_KEY": "your-api-key-here"      }    }  }}

{  "mcpServers": {    "signforge": {      "command": "npx",      "args": ["-y", "@signforge/mcp-server"],      "env": {        "SIGNFORGE_API_KEY": "your-api-key-here"      }    }  }}

Direct (npx)

3. Restart Your Client

Restart Claude Desktop, Claude Code, or Cursor to pick up the new MCP server.

Tools

Envelope Management

Tool	Description
`create_and_send`	Upload a PDF, add a signer, and send for e-signature. Accepts a local file path or base64-encoded PDF.
`check_status`	Check the status of an envelope — see signing progress, timestamps, and available documents.
`list_envelopes`	List your envelopes with optional status filtering (`draft`, `sent`, `completed`, `voided`, `expired`).
`send_envelope`	Send a draft envelope for signing.
`void_envelope`	Void (cancel) an active envelope with an optional reason.
`delete_envelope`	Permanently delete a draft or voided envelope.

Document Downloads

Tool	Description
`download_signed`	Download the signed PDF for a completed envelope to a local file.
`download_certificate`	Download the audit certificate PDF with full audit trail.
`download_archive`	Download a ZIP archive with signed PDF, certificate, and all documents.

Embedded Signing

Templates

Webhooks

Example Conversations

Send a document for signature

You: Send my NDA at ~/Documents/nda.pdf to [email protected] (Jane Smith) for signature.
AI: I'll send that NDA for signature now.
[Uses create_and_send tool]
Done! I've created and sent the envelope:- Envelope ID: a1b2c3d4-...- Status: sent- Jane Smith ([email protected]) will receive a signing link via email.

You: Send my NDA at ~/Documents/nda.pdf to [email protected] (Jane Smith) for signature.
AI: I'll send that NDA for signature now.
[Uses create_and_send tool]
Done! I've created and sent the envelope:- Envelope ID: a1b2c3d4-...- Status: sent- Jane Smith ([email protected]) will receive a signing link via email.

Check status and download

You: Has Jane signed the NDA yet?
AI: Let me check.
[Uses check_status tool]
Yes! Jane signed it on April 7 at 2:15 PM. The envelope is now completed.
You: Great, download the signed copy and the audit certificate.
[Uses download_signed tool][Uses download_certificate tool]
Done! Files saved:- Signed PDF: ~/Documents/nda-signed.pdf- Audit Certificate: ~/Documents/nda-certificate.pdf

You: Has Jane signed the NDA yet?
AI: Let me check.
[Uses check_status tool]
Yes! Jane signed it on April 7 at 2:15 PM. The envelope is now completed.
You: Great, download the signed copy and the audit certificate.
[Uses download_signed tool][Uses download_certificate tool]
Done! Files saved:- Signed PDF: ~/Documents/nda-signed.pdf- Audit Certificate: ~/Documents/nda-certificate.pdf

Use a template with pre-filled fields

You: Send our standard consulting agreement to [email protected].     Pre-fill the company name as "Acme Corp" and the start date as "May 1, 2026".
AI: I'll create that from your consulting agreement template.
[Uses list_templates tool — finds "Consulting Agreement" template][Uses create_from_template tool — with prefill_fields and send_immediately: true]
Done! Envelope created and sent:- Title: Consulting Agreement- Recipient: [email protected]- Pre-filled: company = "Acme Corp", start_date = "May 1, 2026"- Status: sent

You: Send our standard consulting agreement to [email protected].     Pre-fill the company name as "Acme Corp" and the start date as "May 1, 2026".
AI: I'll create that from your consulting agreement template.
[Uses list_templates tool — finds "Consulting Agreement" template][Uses create_from_template tool — with prefill_fields and send_immediately: true]
Done! Envelope created and sent:- Title: Consulting Agreement- Recipient: [email protected]- Pre-filled: company = "Acme Corp", start_date = "May 1, 2026"- Status: sent

Manage envelope lifecycle

You: List my sent envelopes.
[Uses list_envelopes tool with status: "sent"]
You: Void the contract for Project Alpha — the deal fell through.
[Uses void_envelope tool with reason]
You: Now delete it.
[Uses delete_envelope tool]
Done — envelope voided and deleted.

You: List my sent envelopes.
[Uses list_envelopes tool with status: "sent"]
You: Void the contract for Project Alpha — the deal fell through.
[Uses void_envelope tool with reason]
You: Now delete it.
[Uses delete_envelope tool]
Done — envelope voided and deleted.

Set up a webhook

You: Set up a webhook to notify my server when documents are signed or completed.
[Uses create_webhook tool]
Webhook created:- URL: https://api.yourapp.com/webhooks/signforge- Events: envelope.signed, envelope.completed- Secret: whsec_abc123... (save this for signature verification!)

You: Set up a webhook to notify my server when documents are signed or completed.
[Uses create_webhook tool]
Webhook created:- URL: https://api.yourapp.com/webhooks/signforge- Events: envelope.signed, envelope.completed- Secret: whsec_abc123... (save this for signature verification!)

Environment Variables

Variable	Required	Default	Description
`SIGNFORGE_API_KEY`	Yes	—	Your SignForge API key. Get one at signforge.io/dashboard/developers.
`SIGNFORGE_API_URL`	No	`https://signforge.io/api/v1`	API base URL. Only change this for self-hosted instances or staging.

Sandbox Mode

API keys created in sandbox mode will create test envelopes that don't send real emails. Use sandbox mode during development and testing.

Troubleshooting

"SIGNFORGE_API_KEY environment variable is required" Make sure you've set the SIGNFORGE_API_KEY in your MCP client configuration. See the setup instructions above.

"SignForge API error (401)" Your API key is invalid or expired. Generate a new one at signforge.io/dashboard/developers.

"SignForge API error (403)" Your API key doesn't have permission for this operation. Check your key's scopes.

"SignForge API error (429)" You've hit the rate limit. Wait a moment and try again.

Server not showing up in Claude Desktop

Make sure the config JSON is valid (no trailing commas)
Restart Claude Desktop completely (quit + reopen)
Check the MCP server logs in Claude Desktop's developer console

License

MIT

Source: README.md at commit ef6b0d0

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Tool	Description
`list_templates`	List your reusable document templates.
`create_from_template`	Create an envelope from a template with optional pre-filled field values. Send immediately or save as draft.

Tool	Description
`create_webhook`	Subscribe to envelope events (sent, viewed, signed, completed, expired, voided, declined).
`list_webhooks`	List all configured webhooks.
`delete_webhook`	Delete a webhook by ID.

Signforge

Overview

Installation

In SourceWeft

Other MCP clients

README

@signforge/mcp-server

What It Does

Quick Start

1. Get Your API Key

2. Configure Your AI Client

Claude Desktop

Claude Code

Cursor

Direct (npx)

3. Restart Your Client

Tools

Envelope Management

Document Downloads

Embedded Signing

Templates

Webhooks

Example Conversations

Send a document for signature

Check status and download

Use a template with pre-filled fields

Manage envelope lifecycle

Set up a webhook

Environment Variables

Sandbox Mode

Troubleshooting

Links

License

Tools

Version history

Score

More servers like Signforge

DropGone