Skip to main content
Glama
Crackx17

dokutrak-mcp

by Crackx17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to dokutrak-mcp

No user-submitted related servers found.

    Related Servers

    • @dropspot/mcp by officialdropspot

      @dropspot/mcpofficial

      officialdropspot
      A
      license
      B
      quality
      C
      maintenance
      Enables AI clients to create passwordless document intake requests with itemized checklists, dispatch secure upload links, and track completion status. Also supports reviewing and approving or rejecting uploaded files, fetching short-lived download links, and managing client records and reusable checklist templates.
      12
      224 npm
      MIT
    • 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
    • documentero by documentero

      documenteroofficial

      documentero
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to list Documentero templates, inspect their field schemas, and generate Word/PDF/Excel documents via the Documentero API.
      17 npm
      1
      MIT
    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

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: create_request creates and emails, get_request retrieves status, download_documents fetches files as a zip, and request_replacement re-requests rejected files. The descriptions explicitly distinguish their use cases and boundaries, leaving no room for confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: create_request, get_request, request_replacement, download_documents. The convention is predictable and readable throughout.

    Tool Count5/5

    Four tools are well-scoped for the core agent workflows of document request management. Each tool earns its place with no redundancy, and the set avoids both oversupply and critical under-supply.

    Completeness4/5

    The set covers creating, tracking, downloading, and re-requesting documents, which covers the main agent actions. However, there is no tool to list all requests without a search term, nor to update request details (e.g., deadline), representing a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources