Document AI and headless DMS: OCR, IDP, search, workflows, signatures. EU-hosted, OAuth 2.1.
io.github.paperoffice-ai/paperoffice-mcp (Model Context Protocol) Server
This MCP server provides access to a βPaperOfficeβ platform focused on document AI and a headless DMS. Capabilities mentioned include OCR, IDP, search, workflows, and signatures. The service is described as EU-hosted and uses OAuth 2.1 for authentication.
π οΈ Key Features
Document AI
Headless DMS
OCR
IDP
Search
Workflows
Signatures
EU-hosted
OAuth 2.1
π Use Cases
Extract text from documents via OCR
Apply IDP to document data
Search across documents
Run document workflows
Capture or manage signatures
β‘ Developer Benefits
Integrates document AI and DMS functions through MCP
Uses OAuth 2.1 for authentication
Supports building tools around OCR, search, workflows, and signatures
β οΈ Limitations
Tool-level capabilities, endpoints, and exact MCP tools are not described in the provided data.
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.
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.
Four real workflows with Claude β under 30 seconds each. Click a card for the deep-dive with prompts and tool lists:
Use case
Watch & read
π
Month-end invoices β open items across every workspace, with totals and overdue flags
π₯
Overnight inbox β capture, classify, flag duplicates and expiring contracts before you wake up
π±
Mobile contract lookup β signed date, terms, page reference from your phone in seconds
π
Spend dashboard β from 300 invoices to a board-ready dashboard in one prompt
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.
/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β¦
URL
Surface
Good for
Everything
https://mcp.paperoffice.ai/mcp-full
300+
Power users, agents, migration
Documents Operations
https://mcp.paperoffice.ai/dms
300+
Canonical DMS URL
Cursor / Windsurf
https://mcp.paperoffice.ai/cursor
same as /dms
IDE β full Documents Operations including TTS
Grok
https://mcp.paperoffice.ai/grok
curated tool set: the /chatgpt tools without the attachment upload
Grok connector
Meta Muse
https://mcp.paperoffice.ai/muse
same curated tools as /grok
Meta Muse connector
Claude Directory URL
https://mcp.paperoffice.ai/claude
Directory without TTS
Claude Desktop / Anthropic Directory
ChatGPT
https://mcp.paperoffice.ai/chatgpt
curated tool set, every tool listed individually
ChatGPT Apps SDK
ChatGPT alias
https://mcp.paperoffice.ai/openai
same as /chatgpt
Legacy ChatGPT URL
Slim IDE subset
https://mcp.paperoffice.ai/mcp
subset 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
Client
Suggested start
Want 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:
ChatGPT and Claude do not need a repository: connect the /chatgpt or /claude URL directly, or install PaperOffice from their app directories once listed.
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 there without any manual entry.
bash
# Claude Code
claude 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.
Transport: Streamable HTTP (remote MCP) β no stdio, no local process
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)