Claude
PaperOffice MCP for Claude: 300+ API/MCP Tools connected in 10 seconds
Connect guide →MCP
Document AI for AI agents — the PaperOffice MCP server
PaperOffice AI provides a Streamable HTTP MCP server at mcp.paperoffice.ai — 300+ API/MCP Tools for DMS, OCR/IDP, signatures, PDF and workflows, authenticated with a User or Group token (po_ut_ / po_gt_).
At a glance
- 300+API/MCP tools
- 35UI languages
- Full-text +semantic search
- 69ready document types
Made for real business. Not for hype.
Trusted by leading companies worldwide
MCP profiles
One access token — multiple profiles for DMS, OCR/IDP and workflows.
| Endpoint | Tools | Purpose |
|---|---|---|
/dms | 300+ | Canonical headless DMS (CRUD + capture + workflow + signatures + admin) |
/claude | 300+ | Alias of /dms for Claude Desktop / Claude Code |
/mcp | 300+ | Default read-only (Cursor-safe) |
/mcp-document-ai | 300+ | Document AI (lighter) |
/mcp-workflow-ai | 300+ | Workflow AI (tasks, HITL, approvals) |
/mcp-document-workflow-ai | 300+ | Document AI + Workflow AI |
/mcp-fast | 300+ | Minimal fast sessions |
/mcp-full | 300+ | All MCP-enabled tools |
Auth: User/Group token (po_ut_ / po_gt_) or OAuth 2.1 — po_sk_ and po_pk_ are blocked for MCP. Source: llms-full.txt.
Billing is internal in credits; amounts follow the selected currency (base: list price).
For clients
Ready connect guides for common agents.
Cursor
PaperOffice MCP for Cursor: 300+ API/MCP Tools
Connect guide →ChatGPT
PaperOffice MCP for ChatGPT: 300+ API/MCP Tools
Connect guide →Headless DMS
Headless DMS via MCP: 300+ API/MCP Tools
Connect guide →FAQ
How does MCP authentication work?
With a User or Group token (po_ut_ / po_gt_) — po_sk_ and po_pk_ are blocked for MCP — or via OAuth 2.1 on first connect.
What does MCP usage cost?
MCP calls bill credits like the REST API. Balance and usage can be queried via billing endpoints.
What is the difference between read-only and write?
Profiles such as /mcp and /cursor are tuned for safe read sessions. /dms and /claude expose the full write surface including capture and workflow.
Is OAuth 2.1 supported?
Yes. OAuth 2.1 can be used on first connect; Bearer header auth remains available.
What is an MCP-native AI-DMS?
An AI-DMS whose capabilities are natively reachable via the Model Context Protocol — same permissions and workspaces as in the app.
Which clients are supported?
Including Claude, ChatGPT, Cursor and headless DMS profiles — see the connect pages.
How fast is connect?
Typically seconds: enter URL/token and enable tools.
Do profiles differ?
Yes — read-only vs. write and tool scope depend on the MCP profile.
Where is the documentation?
Under /mcp/, developer MCP, and llms.txt / Postman.
Is there EU hosting?
Yes — processing in PaperOffice EU infrastructure.
