Signable MCP server
Related Servers
Alternatives to Signable MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables users to create, manage, and track electronic signing requests and templates through Claude Desktop and other MCP-compatible clients. Provides multi-tenant authentication with customer API keys for secure document workflow operations.66 npm-
- AlicenseAqualityCmaintenanceEnables Claude to create and manage e-signature contracts, including generating PDFs, sending signing links, and checking contract status.60MIT
- AlicenseAqualityBmaintenanceExposes the SumoSign signing API to AI agents, allowing document upload, envelope creation, and tracking, with signing always done by human recipients.1549 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes the ZapSign REST API as MCP tools, enabling LLM-driven document workflows such as creating documents, managing signers, filling templates, running background checks, and handling webhooks.-
- AlicenseAqualityDmaintenanceProvides DocuSign eSignature operations via JWT Grant for headless AI agents, enabling envelope management, document signing, and template access through MCP tools.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage electronic signature documents via the ZapSign API, including sending from PDF, DOCX, URL, or template, tracking status, managing signers, templates, webhooks, background checks, and account settings.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource and scope: contacts, contact envelope history, account envelopes, envelope details, template lists, template details, and users. There is no meaningful overlap that would cause an agent to select the wrong tool.
The naming mostly follows a predictable list_/get_ pattern, with list_ for collections and get_ for single items. The only minor deviation is find_contacts instead of list_contacts, but the convention is otherwise clear and consistent.
Seven tools is well-scoped for a Signable server focused on searching and retrieving account data. Each tool covers a meaningful part of the domain without unnecessary redundancy.
The server covers listing and retrieving contacts, envelopes, templates, and users, but entirely lacks write/send operations. This is especially notable since get_template mentions using it before send_envelope_from_template, yet no send tool exists, leaving a clear workflow dead-end.