mcp-paperless-ngx
Related Servers
Alternatives to mcp-paperless-ngx
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceAn MCP (Model Context Protocol) server for interacting with a Paperless-NGX API server. This server provides tools for managing documents, tags, correspondents, and document types in your Paperless-NGX instance.44730141TypeScriptISC
- FlicenseNot gradedqualityCmaintenanceMCP server for Paperless-ngx document management, enabling search, OCR content access, metadata updates, tag/correspondent/type management, and duplicate detection via natural language.-
- FlicenseAqualityCmaintenanceMCP server for Paperless-ngx document management. Enables AI models to search, retrieve, update documents and manage metadata.7-
- AlicenseNot gradedqualityAmaintenanceA 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
- AlicenseAqualityBmaintenanceAn MCP server that puts a paperless-ngx document archive within reach of AI assistants, enabling full-text search, reading, filing, uploading, and managing documents and taxonomy through the paperless-ngx REST API.1629MIT
- FlicenseAqualityBmaintenanceA 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-
TDQS
Scored across 85 tools
Most CRUD tool families are clearly separated by resource type, but bulk_edit_documents overlaps with rotate_documents, merge_documents, edit_pdf, reprocess_documents, and delete_documents by exposing the same operations as methods. get_document with include_content also partially duplicates get_document_content, so an agent must read descriptions carefully to pick the right tool.
Nearly every tool follows the verb_noun snake_case pattern, with predictable list/get/create/update/delete families for each resource type. Minor exceptions like global_search and search_autocomplete still fit the general verb-first style and do not create confusion.
85 tools is an extreme surface for an MCP server, far beyond the practical range for agent tool selection. Even for a broad domain like Paperless-ngx, this exceeds the 50+ threshold that constitutes an extreme mismatch.
The server covers nearly the entire Paperless lifecycle: document search, content retrieval, metadata editing, OCR reprocessing, merging, trash management, share links, workflows, tasks, and full CRUD for all metadata objects. Minor gaps remain, such as no note update tool, no share-link update tool, and no direct user or mail-rule management.