Skip to main content
Glama
NikhilBelwate

pdf-merger-mcp-server

by NikhilBelwate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pdf-merger-mcp-server

No user-submitted related servers found.

    Related Servers

    • pdfeverything

      Lezheng2333
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform 13 PDF operations (merge, split, compress, watermark, encrypt, and more) on local files via MCP.
      2
      -

    • pdf-toolkit-mcp

      EigenCharlie
      A
      license
      A
      quality
      C
      maintenance
      Provides 18 PDF operations (merge, split, convert, edit, secure, repair, OCR) via iLoveAPI, callable from any MCP client like Claude Code or Claude Desktop.
      18
      35 npm
      1
      MIT

    • PDFSizeAnalyzer-MCP

      wangshuai6491
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive PDF analysis and manipulation including page size analysis, chapter extraction, splitting, compression, merging, and conversion to images. Provides both MCP server interface for AI assistants and Streamlit web interface for direct user interaction.
      -
    • Aspose.PDF Cloud MCP Server by aspose-cloud

      Aspose.PDF Cloud MCP Serverofficial

      aspose-cloud
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables PDF conversion to DOC, merging multiple PDFs, reading document properties, and bundled storage file operations for complete upload-process-download workflows through MCP.
      -
    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.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: upload, remove, merge, and get download URL. There is no overlap in functionality, and the descriptions reinforce the boundaries between them.

    Naming Consistency5/5

    All tool names follow a consistent prefix+verb_noun pattern (pdf_merger_remove_file, pdf_merger_upload_pdfs, pdf_merger_get_download_url). The single exception, pdf_merger_merge, is still a clear verb and fits the overall style.

    Tool Count5/5

    Four tools is a well-scoped size for a PDF merging service. Each tool covers a necessary step in the workflow without redundancy or bloat.

    Completeness4/5

    The core workflow (upload, remove, merge, download) is covered. However, there is no tool to list the current files in a session, which would be needed if an agent needs to reference file IDs without having just uploaded them. This is a minor but notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources