Paperless-NGX MCP Server

Created By
nlouia 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 an interface designed to interact with a Paperless-NGX API server, providing tools to manage documents, tags, correspondents, and document types.

How to use Paperless-NGX MCP Server?

To use the MCP Server, first install it via npm. Then, configure your MCP settings to connect to your Paperless-NGX instance and utilize the functionalities provided by the server to manage your documents.

Key features of Paperless-NGX MCP Server?

  • Management of documents, tags, correspondents, and document types
  • Full-text search capabilities
  • Bulk operations for efficient document management

Use cases of Paperless-NGX MCP Server?

  1. Searching for documents by tags or content.
  2. Uploading new documents into the Paperless-NGX system.
  3. Managing and organizing document metadata efficiently.

FAQ from Paperless-NGX MCP Server?

  • How do I install the MCP server?

Use the npm command: npm install -g paperless-mcp.

  • Can I perform bulk operations on documents?

Yes, the MCP server supports bulk editing for various document operations.

  • Is there an official API documentation available?

Yes, you can refer to the official documentation for detailed information.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nloui
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago