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
      C
      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.
      -

    • paperless-mcp-oidc

      munin92
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables per-user document management and retrieval in Paperless-ngx by authenticating each MCP call with the caller's own Keycloak identity, providing the same 44 tools as the upstream server while maintaining per-person isolation.
      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.8/5.0

    Scored across 50 tools

    Disambiguation4/5

    Tools are grouped clearly by resource and action, so get_document, get_document_content, get_document_metadata, and get_document_notes are easy to distinguish despite all targeting a document by ID. The only mild overlap is list_documents versus search_documents, though their descriptions explain the metadata-filter vs full-text distinction.

    Naming Consistency4/5

    The set overwhelmingly follows a snake_case verb_noun pattern with predictable singular/plural forms: list_*, get_*, create_*, update_*, delete_*, bulk_edit_*. Minor deviations like add_document_note versus get_document_notes and upload_document instead of create_document are understandable but break the otherwise consistent pattern.

    Tool Count2/5

    50 tools is a very large surface for an agent to select from, even though Paperless has many resource types. Several resource groups are only read-only (storage paths, saved views, share links), which makes the high count feel heavier than necessary.

    Completeness3/5

    Documents, correspondents, tags, document types, and custom fields have solid CRUD coverage, and document retrieval/search is thorough. However, storage paths, saved views, and share links expose only list/get operations, and share-link creation is referenced but not present as a tool, leaving notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources