Skip to main content
Glama
pvliesdonk

Paperless MCP

by pvliesdonk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Paperless MCP

No user-submitted related servers found.

    Related Servers

    • paperless-mcp

      subdavis
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with a paperless-ngx document management system through MCP tools, allowing document search, retrieval, upload, and metadata management via natural language.
      -

    • paperless-mcp

      dguastaf
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and retrieve documents from a self-hosted Paperless-ngx instance, including full OCR'd text and metadata, with read-only access enforced via API tokens.
      -

    • 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
    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

    C2.9/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource and action, and the document getters are split into distinct aspects (content, metadata, notes, history, suggestions). The main ambiguity is between get_server_info and get_remote_version, since both expose Paperless version information.

    Naming Consistency4/5

    Names overwhelmingly follow a verb_noun snake_case pattern like list_documents, create_tag, and delete_document_type. Minor inconsistencies exist, such as get_server_info vs. get_remote_version and add_document_note/delete_document_note using add/delete rather than create/delete, but the overall pattern is predictable.

    Tool Count2/5

    50 tools is a very large surface for an MCP server and exceeds the 25+ threshold where tool count starts to hurt usability. While Paperless has many subresources, several of them only have list/get tools, so the set feels heavier and more cluttered than necessary.

    Completeness3/5

    Core resources like documents, tags, correspondents, document types, and custom fields have solid CRUD and bulk-operation coverage. However, storage paths, saved views, and share links only support list and get, with no create/update/delete, leaving noticeable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources