Skip to main content
Glama
Sign In
NamerekT

Paperless-ngx MCP Server

by NamerekT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Paperless-ngx MCP Server

No user-submitted related servers found.

    Related Servers

    • Paperless-NGX MCP Server

      MephistoJB
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing Paperless-NGX documents, tags, correspondents, and document types via natural language. Supports document searching, downloading, uploading, and bulk editing.
      150 npm
      ISC

    • Paperless-NGX MCP Server

      retiform-labs
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP agents to list, query, fetch, and download documents in a Paperless-NGX instance, along with managing tags, correspondents, and document types. Adds bounded content reads — ranged content windows, passage search, and an inline character budget with length metadata — so agents can locate and extract document text without flooding their context.
      45
      459 npm
      ISC

    • paperless-mcp

      tiziano5
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude to a self-hosted Paperless-ngx document archive, enabling natural language search, retrieval, and taxonomy browsing of documents.
      MIT

    • paperless-ngx-mcp

      cbsmiley
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with Paperless-NGX document management through natural language, offering 50 tools for full CRUD operations and management.
      247 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

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct actions or resources, but stats and the list_* tools both report counts for tags, correspondents, and types, which could cause some ambiguity. search/get/download/update/upload are clearly separated.

    Naming Consistency4/5

    Eight tools follow a consistent verb_noun pattern such as search_documents, get_document, list_tags, and upload_document. The exception is 'stats', which breaks the pattern and would be clearer as get_stats or get_summary.

    Tool Count5/5

    Nine tools is well-scoped for a document management server: search, retrieve, download, upload, update, reference-data listers, and a stats summary. Each tool earns its place without feeling redundant.

    Completeness3/5

    Core document operations are covered, including upload, search, get, download, and update, but there is no delete_document and no way to poll the async task ID returned by upload_document. Reference-data creation is only implicitly handled through update_document's create_missing flag.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources