paperless-ngx-mcp
Related Servers
Alternatives to paperless-ngx-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search, inspect OCR content, download, upload, and manage documents in a Paperless-ngx archive through natural language.91MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with Paperless-NGX API servers, supporting document management, tagging, and metadata operations through a natural language interface.65 npm235ISC
- AlicenseNot gradedqualityDmaintenanceEnables managing Paperless-NGX documents, tags, correspondents, and document types via natural language. Supports document searching, downloading, uploading, and bulk editing.65 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude AI to interact with Paperless-NGX document management through natural language, offering 50 tools for full CRUD operations and management.106 npmMIT
- AlicenseCqualityAmaintenanceEnables searching, tagging, uploading, and reading documents in Paperless-NGX, with management of tags, correspondents, document types, and custom fields via MCP tools and resources.501MIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude to a self-hosted Paperless-ngx document archive, enabling natural language search, retrieval, and taxonomy browsing of documents.MIT
TDQS
Scored across 108 tools
Most tools follow a clear resource+action pattern with detailed descriptions that distinguish them, but the sheer scale and a few near-overlapping pairs (list_documents vs search_documents, update_document vs edit_documents_bulk, get_document_suggestions vs get_document_ai_suggestions) could cause misselection without careful reading.
Names are predominantly consistent verb_noun snake_case (list_documents, create_tag, update_document, delete_tag, edit_documents_bulk), with only minor deviations like post_document, restore_from_trash, empty_trash, and merge_documents_as_versions that don't undermine the overall pattern.
At 108 tools, this is far beyond the 25+ threshold that already feels heavy, and the volume risks overwhelming agents even though the Paperless-ngx domain is broad. The exhaustive endpoint-by-endpoint design explains the count, but it would benefit from consolidation into fewer multi-purpose tools.
The surface is remarkably complete, covering documents (single, bulk, versions, notes, trash, share links, downloads, previews), search, tasks, workflows, mail accounts/rules, and all configuration objects. The only minor gap is a missing update operation for document notes, which is easily worked around.