A
licenseNot graded
qualityD
maintenanceEnables managing Paperless-NGX documents, tags, correspondents, and document types via natural language. Supports document searching, downloading, uploading, and bulk editing.
113 npm
ISC
Paperless-ngx MCP Server
by NamerekWASD
Related Servers
Alternatives to Paperless-ngx MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to manage Paperless-NGX documents, tags, correspondents, workflows, and more through the full REST API.109550 npm6ISC
- AlicenseNot gradedqualityFmaintenanceEnables interaction with Paperless-NGX API servers, supporting document management, tagging, and metadata operations through a natural language interface.113 npm237ISC
- AlicenseNot gradedqualityCmaintenanceConnects Claude to a self-hosted Paperless-ngx document archive, enabling natural language search, retrieval, and taxonomy browsing of documents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude AI to interact with Paperless-NGX document management through natural language, offering 50 tools for full CRUD operations and management.550 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with a paperless-ngx document management system through MCP tools, allowing document search, retrieval, upload, and metadata management via natural language.-
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation4/5
Most tools target distinct actions or resources, but stats and the list_* tools both report counts for tags, correspondents, and types, which could cause some ambiguity. search/get/download/update/upload are clearly separated.
Naming Consistency4/5
Eight tools follow a consistent verb_noun pattern such as search_documents, get_document, list_tags, and upload_document. The exception is 'stats', which breaks the pattern and would be clearer as get_stats or get_summary.
Tool Count5/5
Nine tools is well-scoped for a document management server: search, retrieve, download, upload, update, reference-data listers, and a stats summary. Each tool earns its place without feeling redundant.
Completeness3/5
Core document operations are covered, including upload, search, get, download, and update, but there is no delete_document and no way to poll the async task ID returned by upload_document. Reference-data creation is only implicitly handled through update_document's create_missing flag.
Maintenance
ActivitySlowing
ResponsivenessNo issues