Skip to main content
Glama
Sign In
benspdf

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
      B
      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.
      13 npm
      -

    • pdf-toolkit-mcp

      0xmortuex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, read in token-budgeted chunks, search, and extract tables and images from PDFs, plus merge, split, reorder, and rotate pages. Works with pure-Python dependencies and confines all file access to explicitly allow-listed folders.
      MIT

    • pdf-toolbox-mcp

      twoer
      A
      license
      B
      quality
      B
      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
      C
      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
      63 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.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct PDF inspection or artifact management action. The pdf_* tools are clearly separated by function (page count, metadata, text check, extraction, access, layout, render, OCR), and the artifact tools (discard, list, export) serve unique purposes. No overlapping responsibilities.

    Naming Consistency4/5

    PDF tools follow a consistent 'pdf_' prefix with descriptive names (pdf_page_count, pdf_extract_text), but artifact management tools (discard, export, list_artifacts, create_test_pdf_file) lack the prefix and follow a different verb/noun style. The split is understandable but slightly inconsistent.

    Tool Count5/5

    12 tools is well-scoped for a PDF utility server. Each tool fills a distinct role in inspecting and processing PDFs, plus artifact lifecycle management. The count is neither bloated nor thin for the apparent domain.

    Completeness5/5

    The surface covers the essential PDF inspection workflows: determining page count, text presence, extraction, OCR, metadata, access restrictions, page layout, and rendering. Artifact handling (create, list, discard, export) is complete. No obvious missing operations for the server's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources