Skip to main content
Glama
patrickcylai

paperless-ngx MCP server

by patrickcylai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to paperless-ngx MCP server

No user-submitted related servers found.

    Related Servers

    • mcp-paperless-ngx

      Code-Omega-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only and write MCP server for Paperless-ngx, enabling document listing, metadata retrieval, and creation of tags, correspondents, document types, and sorting workflows via natural language.
      MIT

    • paperless-mcp

      chrisguidry
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for your paperless-ngx document archive that lets an AI assistant search documents by full text, tags, correspondents, and dates, and read the text of any document.
      MIT

    • paperlessngx-mcp

      Milli42
      F
      license
      A
      quality
      B
      maintenance
      A privacy-first MCP server for Paperless-ngx that lets an LLM agent search, organize, tag, and reference documents without exposing full text unless explicitly requested.
      13
      -

    • paperless-mcp

      baruchiro
      A
      license
      B
      quality
      A
      maintenance
      An MCP (Model Context Protocol) server for interacting with a Paperless-NGX API server. This server provides tools for managing documents, tags, correspondents, and document types in your Paperless-NGX instance.
      44
      362 npm
      144
      TypeScript
      ISC
    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 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: search, get, download, upload, update, bulk edit, notes, object CRUD, stats, status, and tasks. The api_request escape hatch intentionally overlaps but explicitly directs agents to prefer purpose-built tools. No two tools appear interchangeable.

    Naming Consistency4/5

    Almost all tools follow a clear paperless_verb_noun pattern, making the set easy to scan. Minor deviations include paperless_document_notes, which lacks an action verb, and paperless_api_request, which is noun-like, plus mixed singular/plural object forms.

    Tool Count4/5

    At 16 tools the set sits just above the ideal 3-15 range, but the breadth is justified by paperless-ngx's domain: documents, objects, notes, tasks, stats, and system health. Each tool covers a distinct responsibility with no redundant entries.

    Completeness4/5

    Document lifecycle coverage is strong: search, read, download, upload, update, bulk delete, notes, and suggestions are all present, and object CRUD is covered. However, several secondary areas like trash, permissions, workflows, and document editing are only reachable through the generic api_request escape hatch rather than first-class tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources