Paperless-NGX MCP Server

Created By
baruchiroa year ago
An MCP (Model Context Protocol) server for interacting with a Paperless-NGX API server. This server provides tools for managing documents, tags, correspondents, and document types in your Paperless-NGX instance.
Overview

What is Paperless-NGX MCP Server?

Paperless-NGX MCP Server is a tool designed to manage documents, tags, correspondents, and document types within a Paperless-NGX instance through an AI assistant. It enhances productivity by automating document management tasks.

How to use Paperless-NGX MCP Server?

To use the server, install it via Smithery or manually, configure it with your Paperless-NGX instance URL and API token, and then interact with it through commands to manage your documents.

Key features of Paperless-NGX MCP Server?

  • Seamless document management including searching, uploading, tagging, and bulk editing.
  • Integration with AI for enhanced document handling.
  • Support for various document operations like listing, downloading, and editing.

Use cases of Paperless-NGX MCP Server?

  1. Automating document uploads and organization.
  2. Searching for specific documents using tags or keywords.
  3. Performing bulk edits on multiple documents to streamline management tasks.

FAQ from Paperless-NGX MCP Server?

  • Can I use this server with any Paperless-NGX instance?

Yes, as long as you have the correct URL and API token for your instance.

  • Is there a graphical interface for this server?

No, it operates through command-line interactions and API calls.

  • What programming language is this server built with?

The server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
baruchiro
Star
8
Language
License
ISC license
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago