SignNow MCP Server
OfficialRelated Servers
Alternatives to SignNow MCP Server
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.1495 npmMIT
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to Gmail data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).MIT
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to DocuSign data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp3MIT
- AlicenseBqualityDmaintenanceEnables interaction with the SendForSign API to list document templates and read template content for electronic signature workflows.29 npmMIT
- AlicenseBqualityBmaintenanceeSignatures.com MCP: full control of contract content from your AI. Read and rewrite contracts and templates as Markdown, before and after sending. Send for signature, manage signers, create public signing links and track status. Hosted with OAuth, no install. Pay-per-use, no subscription.1353 PyPI40MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for the Dropbox Sign API supporting signature requests, templates, teams, accounts, events, documents, signers, reports, bulk operations, and workflows.MIT
- AlicenseAqualityCmaintenanceMCP server for DigiSign.cz digital signature API — create, send, and manage digital signature envelopes.151MIT
- AlicenseAqualityDmaintenanceMCP server for the Paraph e-signature API that enables AI tools to fill PDF forms and manage electronic signing workflows. It provides tools for template management, document filling, sending signing requests, and tracking signing progress.712 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server that exposes GroupDocs.Signature as AI-callable tools for signing, verifying, and searching signatures in documents, enabling natural language interaction with document signature operations.MIT
- 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-
- AlicenseAqualityDmaintenanceModel Context Protocol (MCP) server for BoldSign API1495 npm7MIT
TDQS
Scored across 25 tools
Several tool pairs are near-duplicates: send_invite and send_invite_from_template both handle sending an invite from a template or template group, and create_embedded_invite/sending/editor are mirrored by _from_template versions that describe almost identical behavior. Read tools like get_document, get_document_download_link, view_document, and get_signing_link also share very similar naming and can be hard to distinguish at selection time.
Most names follow a clear action_noun snake_case pattern, e.g. send_invite, cancel_invite, list_documents, and get_invite_status. The main exceptions are signnow_skills (no verb), get_document_download_link (clunky/redundant noun), and rename_entity, but these are minor deviations from an otherwise readable and consistent scheme.
At 25 tools this is at the too-many threshold, and the count is inflated by four _from_template variants that appear redundant with the base send_invite and create_embedded_* tools. The server would be better scoped with roughly 15-18 tools, with each covering a distinct workflow.
The sending/signing lifecycle is well covered: upload, fetch, rename, invite, embedded signing, reminders, cancellation, status, and templates. However, there is no delete/remove tool for documents, templates, or groups, and template updates/lifecycle are quite thin. The update_document_fields tool is also narrowly limited to text fields in individual documents.