Developer · Local MCP server
Paperless-ngx
MCP server for Paperless-ngx 3.x — full REST API coverage, schema-aware, token-frugal.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tobee89/mcp-paperless-ngx- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-20
- Updated
- 2026-08-20
- Publisher
- tobee89 (GitHub)
- Repository
- github.com/tobee89/mcp-paperless-ngx
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | mcp-paperless-ngx | 0.1.1 | stdio |
How to connect Paperless-ngx
Paperless-ngx runs locally from a Node.js package published to the npm registry: mcp-paperless-ngx version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y mcp-paperless-ngx@0.1.1. It reads these environment variables: PAPERLESS_URL (required), PAPERLESS_TOKEN (required, secret), PAPERLESS_PUBLIC_URL, PAPERLESS_TOOLSETS, PAPERLESS_READ_ONLY, PAPERLESS_HEADERS, PAPERLESS_DOWNLOAD_DIR, PAPERLESS_MAX_PAGE_SIZE, PAPERLESS_TIMEOUT_MS and PAPERLESS_API_VERSION; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-paperless-ngx": {
"command": "npx",
"args": [
"-y",
"mcp-paperless-ngx@0.1.1"
],
"env": {
"PAPERLESS_URL": "<value>",
"PAPERLESS_TOKEN": "<secret>",
"PAPERLESS_PUBLIC_URL": "<value>",
"PAPERLESS_TOOLSETS": "<value>",
"PAPERLESS_READ_ONLY": "<value>",
"PAPERLESS_HEADERS": "<value>",
"PAPERLESS_DOWNLOAD_DIR": "<value>",
"PAPERLESS_MAX_PAGE_SIZE": "<value>",
"PAPERLESS_TIMEOUT_MS": "<value>",
"PAPERLESS_API_VERSION": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| PandaDoc MCP ServerPandaDoc MCP server for creating, sending, signing, and tracking PandaDoc documents. | Remote · HTTP |
| Panel ReviewGuardian agent for AI coding: four frontier models review risky diffs and commits before they ship. | Remote · HTTP |
| Panini Connector MCPInstall + verify the panini-connector SDK on self-hosted sites, driven by AI agents. | Local · stdio |
| Paparats – Local Semantic Code Search MCPLocal-first semantic code search across all your repos. Private context for AI coding assistants. | Local · HTTP |
| PAPI: Persistent Adaptive Project IntelligenceAdaptive plan/build/review cycles for AI coding assistants, persisted across sessions. | Remote & Local · HTTP, stdio |
| ParallelSandboxRemote Linux boxes for coding agents: Docker, a browser, screenshots, logs, human takeover. | Remote & Local · HTTP, stdio |
| ParaView MCP ServerControl ParaView through arbitrary Python code. | Local · stdio |
| parbakedScaffold invite-only Python/FastAPI apps: auth, admin dashboard, dev server, deploy to fly.io. | Local · stdio |