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.
      3
      -

    • MinerU v4 MCP Server

      Sky6662025
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible agents to convert PDFs and images into Markdown, JSON, HTML, LaTeX, DOCX, or ZIP by wrapping a document parsing service's REST API as callable tools, including uploads, parsing jobs, progress polling, and result downloads.
      1
      Apache 2.0

    • EasyPDF MCP Server

      Lorenzino69
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to edit text inside real PDF files in place while preserving fonts and layout, with a before/after preview. Also supports compressing, merging, splitting, converting, translating, generating and querying PDFs through a hosted remote MCP endpoint.
      MIT

    • 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
    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