paperless-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAPERLESS_URL | Yes | The URL of the Paperless-ngx server, e.g. http://paperless.local:8000 | |
| PAPERLESS_TOKEN | Yes | API token from Paperless-ngx (obtained via /api/token/) | |
| PAPERLESS_TIMEOUT_MS | No | Timeout in milliseconds for API requests (optional, default 15000) | 15000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paperless_healthA | Get Paperless-ngx status (database status and available tasks — connectivity check) |
| search_documentsA | Search Paperless-ngx documents by full-text query, returns summaries with IDs |
| get_documentA | Get the full content and metadata of a single Paperless-ngx document by ID |
| update_documentB | Update metadata fields (title, correspondent, document type, tags, created date) on a Paperless-ngx document |
| list_tagsA | List all tags defined in Paperless-ngx with their IDs and document counts |
| list_correspondentsB | List all correspondents defined in Paperless-ngx with their IDs and document counts |
| list_document_typesA | List all document types defined in Paperless-ngx with their IDs and document counts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear and distinct purpose: retrieving a single document, searching documents, updating documents, listing correspondents/types/tags, and checking health. No overlap or ambiguity.
Tool names consistently follow a verb_noun pattern in snake_case (e.g., get_document, list_tags, search_documents). Even 'paperless_health' follows the pattern with a noun_noun structure, maintaining readability.
With 7 tools, the set is well-scoped for a Paperless-ngx MCP server. It covers core operations without being overwhelming or too sparse.
The tool set is missing crucial operations: no create_document or delete_document, and no ability to create, update, or delete correspondents, document types, or tags. This leaves significant gaps in document lifecycle management.