Skip to main content
Glama
LassiB999

tooldash-mcp

by LassiB999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to tooldash-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      84 PyPI
      1
      MIT

    • 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.
      11 npm
      -

    • benspdf

      benbergner
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to inspect and work with PDF files entirely on the local machine, covering page counts, metadata, layout, encryption permissions, scan-vs-text detection, and page rendering. Generated results land in a temporary workspace as short artifact ids that can be chained between tools and exported to real folders on request.
      12
      1
      Apache 2.0

    • MCP_Documents

      azzindani
      F
      license
      B
      quality
      A
      maintenance
      Enables local, offline document extraction and manipulation—PDF first but also HTML, DOCX, XLSX, PPTX, EML, EPUB, Markdown, and plain text—through tools for probing, locating, extracting, converting, assembling, OCR, protecting, and redacting documents, with nothing leaving the machine.
      7
      -
    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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: reading PDF metadata, merging PDFs, extracting pages, and normalizing text. There is no overlap or boundary ambiguity, so an agent can select the right tool confidently.

    Naming Consistency4/5

    Three tools follow a clear verb_object pattern (merge_pdfs, extract_pdf_pages, clean_text), while pdf_info uses noun_noun rather than a verb-first form. This is a minor inconsistency in an otherwise predictable and readable naming scheme.

    Tool Count4/5

    Four tools is a reasonable size for a focused utility server, and none of the tools feel redundant. The mix of PDF operations with a standalone text cleaner makes the scope slightly broad, but the count itself is not too thin or bloated.

    Completeness4/5

    The PDF workflow covers the key needs of inspection, merging, and page extraction, while clean_text works as a self-contained text utility. Missing operations like PDF text extraction, rotation, or encryption are plausible additions, but agents can complete core merge, extract, and cleanup tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources