AddSign vs Context7
A side-by-side look at the AddSign and Context7 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AddSignDeveloper Tools · Local subprocess (stdio)Send documents for e-signature from templates, track status, remind signers, get signed PDFs.53GoodAuth: api key requiredVerdict: choose AddSign for developer tools work as a local process; choose Context7 for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AddSign when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ADDSIGN_API_KEY, ADDSIGN_BASE_URL. - You want tools like
list_templates, send_for_signature, check_status.
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AddSign | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Not declared | Free |
| Required env vars | ADDSIGN_API_KEYADDSIGN_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 63,150 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 6 | 2 |
| Full listing | View AddSign | View Context7 |
Tools & capabilities
AddSign tools 6
list_templatesTemplates + the signer roles each expects + field summarysend_for_signatureCreate from template + email signers; idempotent via `request_idcheck_statusDocument + per-signer state + recent audit eventsdownload_signed5-minute signed URL + the ledger's SHA-256 for verificationremindNudge pending signers (4h per-signer server-side cooldown)list_documentsPaginated document list, filterable by status
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AddSign
{
"mcpServers": {
"addsign": {
"command": "npx",
"args": [
"-y",
"addsign-mcp"
],
"env": {
"ADDSIGN_API_KEY": "YOUR_ADDSIGN_API_KEY_HERE",
"ADDSIGN_BASE_URL": "YOUR_ADDSIGN_BASE_URL_HERE"
}
}
}
}
Context7
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"ctx7"
]
}
}
}
Frequently asked questions
AddSign is categorized under Developer Tools and uses a local stdio subprocess. Context7 belongs to Developer Tools and uses a local stdio subprocess. Pick AddSign for developer tools work and Context7 for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AddSign has no declared pricing — check the project's own site. Auth: api key required. Context7 is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add addsign and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AddSign has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Context7 has 65/100 (Great) with 9 views, 0 installs and 63,150 GitHub stars.