Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Send documents for legally binding e-signature and manage the reusable templates behind them.
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.
x-api-keyValues 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 …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http apisign https://apisign.io/mcp --header 'x-api-key: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"apisign": {
"url": "https://apisign.io/mcp",
"headers": {
"x-api-key": "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": {
"apisign": {
"type": "http",
"url": "https://apisign.io/mcp",
"headers": {
"x-api-key": "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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
x-api-key secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 against the domain apisign.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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: x-api-key
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
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.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
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 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