Signwell MCP vs Superdocs
A side-by-side look at the Signwell MCP and Superdocs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Signwell MCP for workplace & productivity work as a local process; choose Superdocs for workplace & productivity over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Signwell MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SIGNWELL_API_KEY, SIGNWELL_API_BASE_URL, SIGNWELL_API_TIMEOUT_MS.
Choose Superdocs when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SUPERDOCS_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 57/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | SIGNWELL_API_KEYSIGNWELL_API_BASE_URLSIGNWELL_API_TIMEOUT_MS | SUPERDOCS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Signwell MCP | View Superdocs |
Tools & capabilities
Signwell MCP tools
No tool names declared yet. Check the project README from the listing page.
Superdocs tools
No tool names declared yet. Check the project README from the listing page.
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.
Signwell MCP
{
"mcpServers": {
"bidsketch-signwell-mcp": {
"command": "npx",
"args": [
"-y",
"@signwell/mcp"
],
"env": {
"SIGNWELL_API_KEY": "YOUR_SIGNWELL_API_KEY_HERE",
"SIGNWELL_API_BASE_URL": "YOUR_SIGNWELL_API_BASE_URL_HERE",
"SIGNWELL_API_TIMEOUT_MS": "YOUR_SIGNWELL_API_TIMEOUT_MS_HERE"
}
}
}
}
Superdocs
{
"mcpServers": {
"superdocs": {
"url": "https://api.superdocs.app/v1/agents/signup"
}
}
}
Frequently asked questions
Signwell MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Superdocs belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Signwell MCP for workplace & productivity work and Superdocs for workplace & productivity.
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.
Signwell MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Superdocs is listed as freemium — a free tier with paid plans. 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 bidsketch-signwell-mcp and superdocs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Signwell MCP has a quality signal of 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Superdocs has 41/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.