Skip to main content
Glama
signnow
by signnow

Related Servers

Alternatives to SignNow MCP Server

  • A
    license
    A
    quality
    D
    maintenance
    Enables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.
    14
    95 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    This 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
  • A
    license
    Not graded
    quality
    D
    maintenance
    This 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/mcp
    3
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    eSignatures.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.
    13
    53 PyPI
    40
    MIT

Related Servers

TDQS

A3.5/5.0

Scored across 25 tools

Disambiguation2/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness3/5

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.

Maintenance

ActivityStale
ResponsivenessNo issues