Paperless MCP
Related Servers
Alternatives to Paperless MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables searching, tagging, uploading, and reading documents in Paperless-NGX, with management of tags, correspondents, document types, and custom fields via MCP tools and resources.5062 PyPI1MIT
- AlicenseAqualityCmaintenanceAn 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.1617 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Paperless-ngx document management, enabling search, OCR content access, metadata updates, tag/correspondent/type management, and duplicate detection via natural language.1-
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseBqualityBmaintenanceEnables MCP agents to list, query, fetch, and download documents in a Paperless-NGX instance, along with managing tags, correspondents, and document types. Adds bounded content reads — ranged content windows, passage search, and an inline character budget with length metadata — so agents can locate and extract document text without flooding their context.45ISC
- AlicenseNot gradedqualityCmaintenanceA 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
TDQS
Scored across 6 tools
The three list_* tools target clearly separate metadata types, and search_documents, get_document, and read_document separate discovery, metadata retrieval, and text reading. There is minor overlap because search_documents also returns metadata, but the boundaries remain workable.
All tools use snake_case with a clear verb_noun pattern: list_*, search_documents, get_document, and read_document. The convention is consistent across the entire surface.
Six tools are well scoped for a document lookup/retrieval interface. Each tool has a distinct role, and there is no obvious redundancy or missing slot from a count perspective.
The surface covers listing metadata, searching, metadata retrieval, and reading extracted text, but it is entirely read-only. It lacks core Paperless lifecycle operations such as uploading/creating documents and updating or deleting documents, tags, correspondents, or document types, which will cause failures for common management requests.