Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Send documents for e-signature from AI agents. Upload, sign, and download PDFs.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SIGNFORGE_API_KEY, SIGNFORGE_API_URL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"signforge": {
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add signforge --env SIGNFORGE_API_KEY=your-value --env SIGNFORGE_API_URL=your-value -- npx -y @signforge/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"signforge": {
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"signforge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@signforge/mcp-server"
],
"env": {
"SIGNFORGE_API_KEY": "your-value",
"SIGNFORGE_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SIGNFORGE_API_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 kumarprobeops 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SIGNFORGE_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.2.2)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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