Skip to main content
Glama
benbergner

benspdf

by benbergner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to benspdf

No user-submitted related servers found.

    Related Servers

    • pdf-agent-toolkit-mcp

      abhishektangudu
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform comprehensive PDF operations locally, including compression, text extraction, PII redaction, page organization, splitting, merging, watermarking, creation, and form filling, all without cloud uploads.
      15 npm
      -

    • pdf-toolbox-mcp

      twoer
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to perform local-first PDF processing entirely on-device, including OCR write-back to make scans searchable, unlocking and re-encrypting PDFs, splitting/merging/rotating pages, and compressing files, with no cloud calls or file uploads.
      25
      1
      MIT

    • tooldash-mcp

      LassiB999
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to inspect PDFs, merge or extract pages, and clean text entirely offline through the Model Context Protocol, with no uploads, API keys, or network calls.
      4
      50 npm
      MIT

    • pdfeverything

      Lezheng2333
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform 13 PDF operations (merge, split, compress, watermark, encrypt, and more) on local files via MCP.
      2
      -
    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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each of the six PDF inspection tools targets a genuinely different aspect: page count, metadata stores, text layer/OCR need, encryption/permissions, page geometry, and visual rendering. Descriptions actively cross-reference and delimit each other (e.g. 'for whether pages hold readable text use pdf_check_text'), leaving no real overlap. The workspace tools (discard/list_artifacts/export/create_test_pdf_file) are likewise distinct in purpose.

    Naming Consistency3/5

    Most PDF tools share a 'pdf_' prefix, but verb/noun ordering is inconsistent (pdf_page_count and pdf_metadata are noun-first while pdf_check_text and pdf_render_pages are verb-first), and the four workspace tools drop the prefix entirely (discard, export, list_artifacts, create_test_pdf_file). All snake_case keeps it readable, but the convention is mixed rather than predictable.

    Tool Count5/5

    Ten tools is well-scoped for a PDF utility server, with a coherent split between PDF inspection (six tools), artifact/file lifecycle (three tools), and a test-fixture generator. Each tool earns its place without redundancy.

    Completeness3/5

    Several descriptions explicitly point users to pdf_extract_text and pdf_ocr ('use pdf_extract_text', 'prefer pdf_ocr'), yet neither tool is in the set, so the surface can check for text and render pages but cannot extract text or run OCR. Core inspection and output/export flows are covered, but this text-extraction hole is a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources