Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Send documents for e-signature from AI agents. Upload, sign, and download PDFs.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SIGNFORGE_API_KEY, SIGNFORGE_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"signforge": {
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add signforge --env SIGNFORGE_API_KEY=your-value --env SIGNFORGE_API_URL=your-value -- npx -y @signforge/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"signforge": {
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"signforge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SIGNFORGE_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account kumarprobeops, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SIGNFORGE_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.2) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, debuff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Send documents for e-signature directly from Claude Desktop, Claude Code, Cursor, and other AI agents — powered by SignForge, the free e-signature platform.
This MCP server connects AI agents to SignForge's e-signature API. Your AI assistant can:
Sign up at signforge.io and generate an API key from your Developer Settings.
Choose your client below and add the configuration:
Add to your claude_desktop_config.json:
{
"mcpServers": { "signforge": { "command": "npx", "args": ["-y", "@signforge/mcp-server"], "env": { "SIGNFORGE_API_KEY": "your-api-key-here" } } } }
Config file location:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonclaude mcp add signforge -- npx -y @signforge/mcp-server
Then set the environment variable in your shell:
export SIGNFORGE_API_KEY="your-api-key-here"
Add to your Cursor MCP settings (.cursor/mcp.json):
{
"mcpServers": { "signforge": { "command": "npx", "args": ["-y", "@signforge/mcp-server"], "env": { "SIGNFORGE_API_KEY": "your-api-key-here" } } } }
SIGNFORGE_API_KEY="your-api-key-here" npx -y @signforge/mcp-server
Restart Claude Desktop, Claude Code, or Cursor to pick up the new MCP server.
| 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. |
| 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. |
| Tool | Description |
|---|---|
get_embed_url | Generate an embeddable signing URL for in-app signing experiences. |
| 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. |
You: Send my NDA at ~/Documents/nda.pdf to jane@example.com (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:
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:
You: Send our standard consulting agreement to bob@acme.com.
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:
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: Set up a webhook to notify my server when documents are signed or completed.
[Uses create_webhook tool]
Webhook created:
| 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. |
API keys created in sandbox mode will create test envelopes that don't send real emails. Use sandbox mode during development and testing.
"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
MIT