Skip to main content
Glama
baruchiro

paperless-mcp

by baruchiro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to paperless-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-paperless-ngx

      Code-Omega-Solutions
      A
      license
      Not graded
      quality
      C
      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

    • mcp-paperless-ngx

      tobee89
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server for Paperless-ngx that provides full REST API coverage for document management, including search, upload, metadata, workflows, sharing, and admin, with token-frugal responses and a scoped toolset.
      85
      55 npm
      1
      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
      -
    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

    B3.3/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions clearly differentiate get_document (metadata) vs get_document_content vs get_document_thumbnail vs download_document. However, the document-listing trio (list_documents, query_documents, and the deprecated search_documents) overlaps, forcing the agent to reason about which to pick even though the descriptions do explain the boundary.

    Naming Consistency4/5

    The set follows a strong verb_noun convention (list_/get_/create_/update_/delete_/bulk_edit_ + resource) applied uniformly across tags, correspondents, document types, and custom fields. The only notable deviation is post_document (instead of create_document), a minor inconsistency in an otherwise predictable scheme.

    Tool Count3/5

    At 44 tools this is heavy, well above the typical 3-15 sweet spot, though the breadth is partly justified by six distinct resource domains (documents, tags, correspondents, document types, custom fields, mail). Repetition such as five near-identical bulk_edit_* tools and the deprecated search_documents adds weight without fully earning its place.

    Completeness4/5

    The surface is comprehensive: full CRUD plus bulk operations across all major entities, document content/thumbnail/download, notes, and mail accounts/rules. Minor gaps remain—storage paths are referenced as filters but have no management tools, and single-document deletion is only reachable through bulk_edit_documents' 'delete' method.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources