Overview Overview News News
Share
Grok Bot · Setup guide

Use PaperOffice inside Grok Bot

The same AI-DMS — connected in Grok Bots (desktop or grok.com) via the MCP endpoint /grok. Test instantly with the demo workspace or connect your own account.

Step 1

User token or OAuth

Choose a path. The Grok Bot connection below is identical for both.

Recommended for testing

Try it instantly — no account

Use the shared demo User token (po_gt_) to chat with the prepared demo workspace right away — no registration needed.

Demo User token
po_gt_15_131_3687fbff1cb5a88bc546400c9ce2944904b1acbbd0ef8462

The demo token only grants access to the shared demo workspace. Use the “With account” tab for your own documents.

Connect PaperOffice in Grok Bot

Works in Grok Desktop and grok.com → Bots. There is no Claude-style connector dialog: create the bot, paste the prompt, then authorize on the PaperOffice page.

Step 2

Open Grok Bots and create the bot

In Grok open Bots. Type PaperOffice MCP in the To: field and create the bot. If a bot with this name already exists, open it — do not create a second one.

Bots
PaperOffice MCP
Create

Use this exact name. If the bot already exists, open it instead of creating another.

Step 3

Skip cards A–D and paste the prompt

The bot greets and often offers task cards. Do not pick those cards. Paste the connection prompt with the copy button instead — including the /grok URL.

PaperOffice MCP
The bot greets and asks what to take on first.
You
Connection prompt

Connect PaperOffice MCP using https://mcp.paperoffice.ai/grok. Do not use /dms, /claude, or /chatgpt. Then authorize on the PaperOffice page.

Step 4

Authorize on the paperoffice-grok card

The bot adds https://mcp.paperoffice.ai/grok and shows the paperoffice-grok card. Choose Authorize — that opens the PaperOffice page.

paperoffice-grok MCP server
https://mcp.paperoffice.ai/grok

Ready to authorize

Authorize
Step 5

Authorize on the PaperOffice page

Grok opens a window on mcp.paperoffice.ai. Paste the User token (po_ut_ / po_gt_) from step 1 (demo) or step 03 (own account) and click Authorize. po_sk_ is blocked for MCP. First-time users always see this page — a health check afterwards only means the connection is already live.

Authorize MCP access

Grok is requesting access to your PaperOffice account via MCP.

Return after approval
Grok
Granted capability
Documents and PaperOffice AI tools via MCP

Paste the demo User token from step 1, then click Authorize.

Cancel Authorize
PaperOffice MCP Server — secure connection for AI assistants
Step 6

Start chatting with Grok Bot

PaperOffice is connected. Ask the bot about documents, workspaces or processes — with the sample prompts below.

Sample prompts

Works for the demo workspace and your own account — paste into Grok Bot.

  • Which documents are in my workspace?
  • Summarize the most recent document.
  • Find all invoices and list their amounts.
  • Which contracts contain a notice period?

Enterprise-ready from the first request

  • EU-hosted infrastructure and data residency
  • Bring your own storage — your documents stay yours
  • Granular tools and toolsets instead of blanket access
  • Same permissions and audit trail as the AI-DMS application

Also works with Claude, ChatGPT and Cursor

The MCP connector is not limited to Grok — the same PaperOffice endpoints work in every MCP-capable client.

GrokClaudeChatGPTCursorGemini

Ready to connect PaperOffice to Grok Bot?

Set it up once, then use the entire document management directly inside Grok Bot.

Where would you like to try PaperOffice?

Workspace and Playground are built for the computer. Grids, batch processing, and the API Playground need a wide screen and a keyboard.

Workspace on the computer. On the phone: capture and approve.

Send to yourself by email Open PaperOffice Mobile
Register free Open app PaperOffice App The full product: web, desktop, and mobile. Capture, organize, search, and work on documents with your team. Free account required Open playground Playground Try selected functions immediately — without registration, using a restricted demo API key. No registration, but a restricted demo API key