Skip to main content
Glama
Sign In
PDFGate MCP Server

PDFGate MCP Server

Official
by pdfgate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PDFGate MCP Server

No user-submitted related servers found.

    Related Servers

    • 1pdf

      WendongAI
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to perform PDF operations like merge, split, compress, convert, encrypt, OCR, and summarize using natural language.
      98
      8 npm
      MIT
    • pdf4me-mcp

      pdf4me-mcpofficial

      pdf4me
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to perform a wide range of PDF processing tasks, including conversion, editing, merging, splitting, OCR, barcode/QR code generation and reading, AI-powered data extraction, and image processing, through the PDF4me API.
      92
      MIT

    • omapdf-mcp

      pbergin11
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents tools to read PDFs, list form fields, apply operations, highlight, add notes, fill fields, place signatures, list signatures, and flatten PDFs.
      1
      AGPL 3.0
    • PDFMonkey MCP Server

      PDFMonkey MCP Serverofficial

      pdfmonkey
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to generate PDFs from templates using the PDFMonkey API, including managing templates, documents, and Liquid snippets, and checking workspace and quota details.
      11
      97 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

    A3.7/5.0

    Scored across 27 tools

    Disambiguation4/5

    The surface splits cleanly into four resource families (documents, recipients, envelopes, webhooks), and the descriptions proactively resolve the few confusable pairs (download_file vs get_document, delete_document vs delete_envelope, delete_recipient vs remove_recipient_signature, create_embed_link vs send_envelope). The remaining risk is the four transform tools (protect_pdf, flatten_pdf, compress_pdf, watermark_pdf), which are only distinguishable by reading the names closely, but their purposes are in fact distinct.

    Naming Consistency5/5

    Every one of the 27 tools follows a snake_case verb_noun pattern (create_/get_/list_/update_/delete_/remove_/send_/void_ plus a resource), with no camelCase or bare-noun outliers. Domain-specific verbs (protect_pdf, flatten_pdf, watermark_pdf) still conform to the same verb_resource shape.

    Tool Count3/5

    27 tools is on the heavy side, though the server genuinely spans three loosely coupled domains: PDF manipulation (~10 tools), recipients with automatic signing (7), envelopes (6) and webhooks (3). Each tool does earn roughly its place, but the document-processing group could plausibly have been consolidated into a single parameterized transform tool.

    Completeness3/5

    Recipients have full CRUD plus listing and signature lifecycle support, but the other families are missing key discovery/lifecycle operations: there is no list_documents, list_envelopes, or list_webhooks, and no update_envelope or webhook update. An agent can create and fetch by ID but cannot enumerate resources, which is a real dead end for discovery workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources