PaperOffice AI

io.github.paperoffice-aiPublished by GitHub account paperoffice-aiv3.7.0Updated Nov 6, 2026

Document AI and headless DMS: OCR, IDP, search, workflows, signatures. EU-hosted, OAuth 2.1.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageData & Analytics

Overview

AI-generated overview

PaperOffice AI connects an assistant to a hosted document management system for OCR, extraction, search, classification, signing and workflow tasks.

What you can do
  • Search, read, upload, move, version, tag and sign documents in a headless DMS
  • Run OCR in 120+ languages with layout-aware searchable PDF and Markdown output
  • Extract and classify documents zero-shot, chat with documents, redact PII
  • Work with tasks, human-in-the-loop approvals and process automation
  • Query knowledge graph, entities, analytics and BI dashboards
  • Switch between tool catalogs (dms, cursor, claude, chatgpt, grok, muse, mcp, mcp-full) to control how many tools are exposed
When to use it
Useful when documents live in a PaperOffice workspace and you want an assistant to find, read, extract from, classify, sign or report on them in plain language, including invoice and contract workflows across workspaces.
Requirements
A PaperOffice account (free plan available). Remote endpoint over Streamable HTTP with OAuth 2.1 sign-in, or a User token (po_ut_) or Group token (po_gt_) supplied as PAPEROFFICE_API_KEY. Local stdio clients run the npm package via npx; PAPEROFFICE_MCP_LANE optionally selects the tool catalog. Network access to the PaperOffice hosts.
Before you install
The token grants access to your documents and workspaces, so treat PAPEROFFICE_API_KEY as a secret; system keys (po_sk_) and publishable keys (po_pk_) are rejected. Tools can upload, move, version, sign and delete-like modify documents and run workflows, so review write actions. Usage is pay-per-use with credits, and document content is processed by the hosted PaperOffice service in the EU.

Installation

In SourceWeft

  1. Open PaperOffice AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.paperoffice-ai%2Fpaperoffice-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "paperoffice-ai": {
      "type": "http",
      "url": "https://mcp.paperoffice.ai/dms"
    }
  }
}

README

[PaperOffice AI]

PaperOffice MCP Server

Give your AI assistant access to your documents — in plain language, in under 60 seconds.

Search, read, OCR, classify, extract, sign and analyse documents straight from Claude, Claude Cowork, Cursor, ChatGPT, Grok or Windsurf. No SDK, no boilerplate, no local install — or, for stdio-only clients, one npx command.

[Model Context Protocol] [MCP tools] [Hosting] [Auth]

Get started free → · Documentation · Live Postman

Why this matters

Your documents live in a DMS. Your AI assistant lives in your IDE or chat window. PaperOffice connects the two through the Model Context Protocol — so you can just ask, and the model does the work across every authorized workspace.

text
"List all unpaid invoices across my workspaces, with totals and overdue flags.""OCR this scanned contract and extract the signing date and parties.""Classify these 50 documents and file them by type."

No prompt engineering, no API code — the model picks the right PaperOffice tool and runs it.

See it in action

[Claude Fable 5 + PaperOffice MCP DMS — agentic document work]

Claude Fable 5 + PaperOffice MCP DMS — agentic document work. Watch the full guide →

Four real workflows with Claude — under 30 seconds each. Click a card for the deep-dive with prompts and tool lists:

Use caseWatch & read
📊Month-end invoices — open items across every workspace, with totals and overdue flags[Month-end invoices]
📥Overnight inbox — capture, classify, flag duplicates and expiring contracts before you wake up[Overnight inbox]
📱Mobile contract lookup — signed date, terms, page reference from your phone in seconds[Mobile contract lookup]
📈Spend dashboard — from 300 invoices to a board-ready dashboard in one prompt[Spend dashboard]

60-second setup

1 · Auth

You need a PaperOffice account — the free plan is enough to try everything here. No account yet? Create one at app.paperoffice.ai/en/register/ (no credit card).

Claude, ChatGPT and Grok start with OAuth 2.1: the client opens the PaperOffice sign-in, you approve, no token in any file. For Cursor, DMS, or as an alternative: sign in at app.paperoffice.ai, open Account → API and create a User token (po_ut_) or a Group token (po_gt_, limited to the workspaces of one group). po_sk_ and po_pk_ are blocked for MCP.

Questions or something not working: Help & FAQ · Support · Issues.

2 · Paste one URL into your client

Claude Desktop / Anthropic Directory (OAuth 2.1, no key in file) — configs/claude_desktop_config.json

json
{  "mcpServers": {    "paperoffice": {      "url": "https://mcp.paperoffice.ai/claude"    }  }}

/dms and /cursor share the Documents Operations catalog (including TTS). /claude is Directory without TTS. /chatgpt (alias /openai) lists a curated tool set for ChatGPT, every tool individually; /grok and /muse list the same tools except the ChatGPT-only attachment upload.

Full headless DMS (po_ut_ / po_gt_) — configs/dms_mcp.json → /dms. Same catalog as /cursor.

ChatGPT / Grok / Meta Muse (OAuth 2.1, no key in file) — /chatgpt (alias /openai), /grok (configs/openai_mcp.json, configs/grok_mcp.json) or /muse. These three list a curated tool set, every tool individually. po_ut_ / po_gt_ remains an alternative for /chatgpt.

Everything (300+ MCP tools across every module) — configs/mcp_full.json → /mcp-full.

3 · Ask away

That's it — your AI now works with your documents.

Choose your scope — you decide, not your client

Any client can use any URL. The paths below are convenience profiles, not limits: go full from day one, or pick Directory / ChatGPT policy surfaces when a catalog requires it.

I want…URLSurfaceGood for
Everythinghttps://mcp.paperoffice.ai/mcp-full300+Power users, agents, migration
Documents Operationshttps://mcp.paperoffice.ai/dms300+Canonical DMS URL
Cursor / Windsurfhttps://mcp.paperoffice.ai/cursorsame as /dmsIDE — full Documents Operations including TTS
Grokhttps://mcp.paperoffice.ai/grokcurated tool set: the /chatgpt tools without the attachment uploadGrok connector
Meta Musehttps://mcp.paperoffice.ai/musesame curated tools as /grokMeta Muse connector
Claude Directory URLhttps://mcp.paperoffice.ai/claudeDirectory without TTSClaude Desktop / Anthropic Directory
ChatGPThttps://mcp.paperoffice.ai/chatgptcurated tool set, every tool listed individuallyChatGPT Apps SDK
ChatGPT aliashttps://mcp.paperoffice.ai/openaisame as /chatgptLegacy ChatGPT URL
Slim IDE subsethttps://mcp.paperoffice.ai/mcpsubset of 300+Read-safe default for tool-limited IDEs

Client shortcuts: https://mcp.paperoffice.ai/cursor = same Documents Operations catalog as /dms · https://mcp.paperoffice.ai/grok = curated /chatgpt tools without the ChatGPT-only attachment upload · https://mcp.paperoffice.ai/muse = Meta Muse connector, same tools as /grok · https://mcp.paperoffice.ai/claude = Directory without TTS · https://mcp.paperoffice.ai/chatgpt = ChatGPT connector (alias https://mcp.paperoffice.ai/openai) · https://mcp.paperoffice.ai/mcp = slim IDE subset.

Why scopes at all? Fewer tools = faster, more accurate tool-selection by the model, and some clients enforce a tool-count cap. /mcp is the slim IDE subset. None of this limits what PaperOffice can do — switch to /mcp-full anytime for media, CRM and telephony.

Ready-made config files for every profile are in configs/.

Per-client quick reference

ClientSuggested startWant more?
Claude Desktop/claude (OAuth, Directory without TTS)/mcp-full for media/CRM
Claude Cowork / Claude Code/dms (Documents Operations, po_ut_ / po_gt_)/mcp-full for all modules
Cursor / Windsurf/cursor (same catalog as /dms)/mcp-full for media/CRM
ChatGPT/chatgpt (OAuth, alias /openai)/mcp-full for all 300+
Grok/grok (OAuth, curated tool set)/mcp-full for all 300+

These are starting points — change the URL whenever your task needs a different scope.

Marketplace plugins

Prefer a one-click install? The same server is packaged as a plugin for two marketplaces:

MarketplaceRepositoryEndpoint
Cursor Marketplacepaperoffice-ai/paperoffice-cursor-plugin/cursor — token set as a plugin variable, never in the repo
xAI Plugin Marketplace (Grok Build)paperoffice-ai/paperoffice-grok-plugin/grok — OAuth 2.1 on first connection

ChatGPT and Claude do not need a repository: connect the /chatgpt or /claude URL directly, or install PaperOffice from their app directories once listed.

npm package for stdio clients

Clients that only start local (stdio) MCP servers — or teams that prefer one command over a URL — use the npm package @paperoffice-ai/mcp. It is a dependency-free bridge to the same lanes; source in npm/.

json
{  "mcpServers": {    "paperoffice": {      "command": "npx",      "args": ["-y", "@paperoffice-ai/mcp"],      "env": { "PAPEROFFICE_API_KEY": "po_ut_…" }    }  }}
bash
# Claude Codeclaude mcp add paperoffice -e PAPEROFFICE_API_KEY=po_ut_… -- npx -y @paperoffice-ai/mcp
# Test a token and list the toolsPAPEROFFICE_API_KEY=po_ut_… npx -y @paperoffice-ai/mcp --check

Pick another catalog with --lane mcp-full (or claude, chatgpt, grok, muse, mcp, cursor). Configs for VS Code, Windsurf, Cline, Gemini CLI and Codex CLI: npm/README.md.

Official MCP Registry

PaperOffice is published in the official MCP Registry as io.github.paperoffice-ai/paperoffice-mcp — the manifest is server.json in this repository. Clients and directories that read the registry (VS Code, Glama, PulseMCP and others) find the seven lanes and the npm package there without any manual entry.

bash
# Claude Codeclaude mcp add --transport http paperoffice https://mcp.paperoffice.ai/dms

Agent Skills

The MCP server supplies the tools; paperoffice-ai/paperoffice-skills supplies the procedures — five SKILL.md files (API integration, invoice extraction, OCR, documents, tool discovery) that load as a Claude Code plugin, a claude.ai skill upload, or inside the Cursor plugin.

What you can do

AreaExamples
Document AI / IDPZero-shot extraction, classification, document chat, PII redaction
OCR120+ languages, layout-aware, searchable PDF & Markdown output
Headless DMSSearch, read, upload, move, version, tag, sign
Workflow AITasks, human-in-the-loop approvals, process automation
IntelligenceKnowledge graph, entities, analytics, BI dashboards

Why PaperOffice

  • EU-sovereign — own data center in the EU (Navarra, Spain). GDPR-aligned, no mandatory US cloud.
  • Zero-shot IDP — extraction without template training, powered by specialized LLMs.
  • Pay-per-use — transparent credits, no per-seat lock-in.
  • API-first — 300+ API/MCP-Tools via REST or MCP. MCP uses OAuth 2.1 or a User token (po_ut_ / po_gt_) — see Postman.
  • 24+ years — document management since 2002.

Prefer plain REST?

Paste this into any AI assistant for the full API — it reads the docs and writes the code:

text
https://api.paperoffice.ai/latest/docs/postman

Machine-readable context: paperoffice.ai/llms.txt · api.paperoffice.ai/latest/docs/llms.txt

Technical notes

  • Transport: Streamable HTTP (remote MCP). Optional stdio bridge for local-only clients: npx -y @paperoffice-ai/mcp
  • Base host: mcp.paperoffice.ai
  • Auth: OAuth 2.1 first for Claude / ChatGPT / Grok (no token in the file). Bearer (po_ut_ / po_gt_) for Cursor, DMS, and as an alternative. po_sk_ and po_pk_ are blocked for MCP.
  • Public claim: 300+ API/MCP-Tools (unified REST + MCP). Do not cite 250/260/350/357/500 or drifting profile integers.
  • Claude.ai network allowlist: mcp.paperoffice.ai and api.paperoffice.ai (two fs — never paperofice)

Resources

License

Config files and the npm bridge in this repository are MIT. The PaperOffice AI platform and API are proprietary — see paperoffice.ai for terms.

Source: README.md at commit 62e6d76

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v3.7.0LatestOct 23, 2026
  2. v3.6.0Oct 15, 2026
  3. v3.5.0Sep 26, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts