Skip to main content
Glama
mikeysrecipes

eSignatures MCP Server

by mikeysrecipes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to eSignatures MCP Server

No user-submitted related servers found.

    Related Servers

    • BoldSign MCP Server

      Synctest-hub
      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
      31 npm
      MIT
    • DottedSign MCP by DottedSign-Official

      DottedSign MCPofficial

      DottedSign-Official
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.
      142
      -
    • Formify MCP by formify-e-sign

      Formify MCPofficial

      formify-e-sign
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.
      5
      MIT

    • Aoexl Sign

      aryansingh0203
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action combination: contracts, templates, or template collaborators. Contract lifecycle tools are clearly separated from template tools, and collaborator tools are unambiguous.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (create_contract, query_template, delete_contract). Minor variants like list_recent_contracts and add_template_collaborator still fit the overall convention cleanly.

    Tool Count5/5

    13 tools is well-scoped for an e-signature server covering contracts, templates, and template collaboration. Each tool has a clear purpose without excessive overlap or bloat.

    Completeness4/5

    The server covers contract creation, retrieval, listing, deletion, and withdrawal, plus full template CRUD and collaborator management. Minor gaps exist, such as no explicit update/send contract endpoint or resend/remind capability, but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources