Skip to main content
Glama
NamerekWASD

Paperless-ngx MCP Server

by NamerekWASD

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAPERLESS_URLYesBase URL of the Paperless-ngx instance
PAPERLESS_TOKENYesPaperless API authentication token
PAPERLESS_DOWNLOAD_DIRNoPath where downloaded documents will be saved

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_documentsA

Search documents in Paperless.

query Full-text search query across content and title tags List of tag names (document must have all specified tags) correspondent Correspondent name document_type Document type name created_after Date YYYY-MM-DD, strictly after created_before Date YYYY-MM-DD, strictly before limit Maximum number of records to return

get_documentC

Retrieve document metadata and extracted OCR text by ID.

download_documentB

Download document file to local disk.

original True for original uploaded file, False for archived PDF version save_as Full target path; defaults to PAPERLESS_DOWNLOAD_DIR

list_tagsA

List all tags with document counts.

list_correspondentsA

List all correspondents with document counts.

list_document_typesA

List all document types with document counts.

statsA

Archive summary: counts of documents, tags, correspondents, types, and storage paths.

update_documentA

Update document title, correspondent, type, and tags.

correspondent / document_type — name or ID; empty string "" clears the field. add_tags / remove_tags — lists of tag names. create_missing — whether to create missing tags/correspondents/types automatically.

upload_documentA

Upload a file to Paperless.

file_path Local path to PDF/image on this machine created Document date YYYY-MM-DD Returns task ID — processing and OCR run asynchronously in the background.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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