Swiftsign MCP vs Ipybox
A side-by-side look at the Swiftsign MCP and Ipybox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Swiftsign MCP for code execution work as a local process; choose Ipybox for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Swiftsign MCP when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
- You want tools like
swiftsign_signup, swiftsign_send_envelope, swiftsign_confirm_send.
Choose Ipybox when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 57/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 76 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Swiftsign MCP | View Ipybox |
Tools & capabilities
Swiftsign MCP tools 11
swiftsign_signupCreate a sandbox SwiftSign account and get a test API key (no browser needed). Returns an sk_test_ key for sandbox sends — upgrade with swiftsign_upgrade for live. Set the returned key as SWIFTSIGN_API_KEY to use the other tools.swiftsign_send_envelopeSend a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (percent, top-left origin) OR an anchor string, not both. After everyone signs, retrieve the sealed PDF with swiftsign_download_signed_pdf.swiftsign_confirm_sendDispatch a DRAFT envelope — use after a human has reviewed an envelope that swiftsign_send_envelope or swiftsign_send_from_template returned as draft_pending_confirmation. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED.swiftsign_send_from_templateSend an envelope from a saved template by assigning signers to roles. Sandbox keys (sk_test_) send immediately; LIVE keys create a DRAFT for human review unless confirm: true — nothing is emailed until confirmed.swiftsign_check_statusCheck the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.swiftsign_list_envelopesList envelopes (sent documents) with their status. Scoped to your key's mode — sandbox (sk_test_) keys see test envelopes, live keys see live.swiftsign_void_envelopeCancel/void an envelope that hasn't been completed yet. Signers can no longer sign a voided envelope. Works in both sandbox (sk_test_ keys) and live.swiftsign_download_signed_pdfDownload the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those.swiftsign_upgradeInitiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.swiftsign_create_embedded_urlMint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt. The envelope must already be SENT. Works in both sandbox (sk_test_ keys) and live.swiftsign_list_templatesList your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.
Ipybox 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.
Swiftsign MCP
{
"mcpServers": {
"mcp-43": {
"command": "npx",
"args": [
"-y",
"swiftsign-mcp"
]
}
}
}
Ipybox
{
"mcpServers": {
"ipybox": {
"command": "uvx",
"args": [
"ipybox"
]
}
}
}
Frequently asked questions
Swiftsign MCP is categorized under Code Execution and uses a local stdio subprocess. Ipybox belongs to Code Execution and uses a local stdio subprocess. Pick Swiftsign MCP for code execution work and Ipybox for code execution.
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.
Swiftsign MCP has no declared pricing — check the project's own site. Ipybox has no declared pricing — check the project's own site. 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 mcp-43 and ipybox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Swiftsign MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Ipybox has 41/100 (Fair) with 3 views, 0 installs and 76 GitHub stars.