Skip to main content
Glama
benjammartin

RemplirPDF MCP server

by benjammartin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to RemplirPDF MCP server

No user-submitted related servers found.

    Related Servers

    • RentSmart MCP

      rashhh22
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to generate rental agreements and receipts as PDFs through an AI-powered WhatsApp bot. Provides stamp duty information lookup and handles rental document creation with customizable templates.
      -

    • Property MCP Server

      digitsouler
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to operate property management systems via natural language, covering repair orders, owner info, payments, notices, and inspections. Features a full agentic workflow with human-in-the-loop and observability.
      MIT
    • layerone-mcp by GOLayerone

      layerone-mcpofficial

      GOLayerone
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to generate documents (PDF/DOCX/Factur-X) and manage electronic signatures (eIDAS/PAdES) via natural language using LayerOne's DocX and Sign APIs.
      20
      38 npm
      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.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: listing vs. describing templates, generating documents, listing documents, and fetching download links. The descriptions explicitly cross-reference each other (e.g., 'use list_templates for the slug, get_template for fields') and clarify boundaries. No two tools overlap in purpose.

    Naming Consistency5/5

    All five tools follow a clean verb_noun snake_case pattern: get_template, list_templates, generate_document, list_documents, get_download_link. The convention is uniform throughout with no deviations.

    Tool Count5/5

    Five tools is well-scoped for a document-generation service. Each tool earns its place in the discovery-to-download workflow without redundancy or thin coverage.

    Completeness4/5

    The surface covers the full lifecycle: list/describe templates, generate (with in-place update via document_id), list documents, and retrieve download links. The only minor gap is the absence of a delete_document operation, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources