Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Send documents for legally binding e-signature and manage the reusable templates behind them.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
x-api-key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http apisign https://apisign.io/mcp --header 'x-api-key: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"apisign": {
"url": "https://apisign.io/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"apisign": {
"type": "http",
"url": "https://apisign.io/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
x-api-key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 apisign.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:x-api-key
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AI Deprecations
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Send documents out for legally binding e-signature, and manage the templates they come from, directly from an AI agent.
APISign runs a hosted Model Context Protocol server at `https://apisign.io/mcp`. There is nothing to install and nothing to self-host — point your client at the URL, give it an API key, and your agent can draft a contract from a template, fill its variables, send it to signers, and watch the signatures come in.
This repository holds the connection metadata and client configuration. The service itself lives at apisign.io.
1. Get an API key. Sign in at apisign.io, then go to Account → API Keys and create one. Copy it — it is shown once.
Pick the permission deliberately:
| Permission | What the agent can do |
|---|---|
| Read Only | List and read templates and contracts. Nothing else. |
| Read & Write | Everything, including sending contracts, which charges your balance. |
A Read Only key does not merely refuse the write tools — they are left out of the tools/list response entirely, so the agent never learns they exist. If your agent only needs to look things up, use one.
2. Add the server. The quickest route, which works for Claude, Cursor, ChatGPT and most other clients:
npx add-mcp https://apisign.io/mcp --header '{"x-api-key": "your-api-key-here"}'
Or configure it by hand:
{
"mcpServers": { "apisign": { "url": "https://apisign.io/mcp", "headers": { "x-api-key": "your-api-key-here" } } } }
| Client | Config file |
|---|---|
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
| Cursor | ~/.cursor/mcp.json, or %USERPROFILE%\.cursor\mcp.json |
| ChatGPT | Settings → Features → MCP servers → Add MCP server |
Transport is Streamable HTTP. Authentication is the x-api-key header.
Twelve tools, in two families. Everything is scoped to the organization the API key belongs to.
| Tool | Access | What it does |
|---|---|---|
template_list | read | List all templates in the organization. |
template_get | read | Fetch one template by ID, with its content and field definitions. |
template_create | write | Create a blank template from a name and optional Markdown. |
template_update | write | Change a template's name, content, or fields. |
template_upload | write | Convert a base64-encoded DOCX/DOC into a template. |
template_archive | write | Soft-delete a template. |
| Tool | Access | What it does |
|---|---|---|
contract_list | read | List contracts, optionally filtered by status. |
contract_get | read | Fetch one contract, including every signer and their status. |
contract_create | write | Create a contract from a template or from raw content, with signers. |
contract_update | write | Edit a draft contract's details or signers. Drafts only. |
contract_send | write | Send a contract for signing. Charges your balance and emails the signers. |
contract_cancel | write | Cancel a draft or sent contract. |
Templates are Markdown with Handlebars-style variables — {{client_name}}, {{effective_date}} — that contract_create fills in. Signature placeholders work the same way: a one-signer document needs a {{signature}}, and a multi-signer document gives each party their own, assigned through signer_fields.
Draft an NDA for Acme Corp from our standard mutual NDA template, effective
the first of next month, and send it to legal@acme.example and to me.
The agent calls template_list to find the template, template_get to read its variables, contract_create to fill them and attach both signers, then contract_send. You get back a contract ID you can follow with contract_get.
| File | Consumed by |
|---|---|
server.json | The official MCP registry — published as io.apisign/apisign. |
plugins/apisign/mcp.json | Cursor and other Agent Plugins clients. |
glama.json | Glama's indexer. |
The server also serves its own card, without authentication, so directories can describe it without an API key:
https://apisign.io/.well-known/mcp.jsonhttps://apisign.io/.well-known/mcp/server-card.jsonIssues with the MCP integration are welcome here. Questions about your account belong at apisign.io.
MIT