What the connector does
MCP (Model Context Protocol) is an open standard through which an AI assistant uses the tools of another system. PaperOffice provides a remote MCP server for this. Once connected, an assistant such as Claude can work with the documents in your PaperOffice workspaces: search, read, summarize, extract data, upload, rename, move, request signatures and start workflows, always with your PaperOffice permissions.
There is nothing to install. The assistant connects to a URL, you sign in with your PaperOffice account, and the PaperOffice tools appear inside the chat.
Supported assistants and connector URLs
- Claude (claude.ai, Claude Desktop, Claude Code):
https://mcp.paperoffice.ai/claude, sign-in with OAuth 2.1. - ChatGPT:
https://mcp.paperoffice.ai/chatgpt, sign-in with OAuth 2.1. - Grok:
https://mcp.paperoffice.ai/grok, sign-in with OAuth 2.1. - Cursor:
https://mcp.paperoffice.ai/cursor, with a personal user token or a group token.
The profiles point to the same server and differ only in the scope of tools.
What you need
- A PaperOffice account with at least one workspace.
- Credits on the account. Tool calls are billed like API calls.
- An assistant plan that allows connectors, for example Claude Pro, Max, Team or Enterprise. In Team and Enterprise plans, an administrator may have to enable the connector first.
Connect Claude
- In claude.ai, open Settings → Connectors.
- Choose Add custom connector, enter the name PaperOffice and the URL
https://mcp.paperoffice.ai/claude. Leave client ID and secret empty; the OAuth sign-in starts automatically. - Choose Connect and sign in with your PaperOffice account. Review the requested access and confirm.
- In the chat, enable the PaperOffice tools for the conversation.
Claude Desktop uses the same connector list as claude.ai. In Claude Code, add the server with claude mcp add --transport http paperoffice https://mcp.paperoffice.ai/claude and complete the sign-in with /mcp.
A first test: ask “Which PaperOffice workspaces can I access?” Claude should list your workspaces.
Connect ChatGPT and Grok
ChatGPT: open Settings → Connectors, add a custom connector with the name PaperOffice, the URL https://mcp.paperoffice.ai/chatgpt and OAuth as authentication, then connect and sign in. Depending on your plan, developer mode may have to be enabled for custom connectors. The ChatGPT profile is a curated selection of tools; it contains, for example, no signature and no workflow tools.
Grok: open grok.com/connectors, create a custom connector with the URL https://mcp.paperoffice.ai/grok and sign in with your PaperOffice account on the first connect. The Grok profile is also a curated selection of tools.
Connect Cursor with a token
- Sign in to the PaperOffice app and open Account → API.
- Create a user token or use a group token from your administrator. You can view and copy the token on the API page at any time; keep it safe.
- Add the server to the mcp.json file of Cursor with the URL
https://mcp.paperoffice.ai/cursorand the token as a bearer token in the Authorization header. - Restart Cursor or reload the MCP servers.
Never commit an mcp.json file with a real token to a repository. Secret keys and publishable keys of the REST API are blocked for MCP.
Permissions: the assistant never gets more than you
The assistant works with the permissions of the signed-in PaperOffice user. Workspace membership, roles, shared folders, retention rules (WORM) and legal holds apply unchanged. A read-only user in PaperOffice stays read-only in the assistant.
Every tool carries a title and hints whether it only reads or changes something. The assistant uses these hints to ask you before it acts. Deleting, emptying the trash and sending signature requests are marked as destructive, so expect a confirmation question. Deleted documents go to the PaperOffice trash first and can be restored in the app.
Account settings, billing, user management and the creation of API keys are not available through the connector. They stay in the PaperOffice app.
Data flow: what the assistant sees and what PaperOffice receives
- You write a request in the assistant.
- The assistant decides which PaperOffice tool to call and sends the parameters, for example a search term or a document ID, to the PaperOffice MCP server.
- PaperOffice runs the call with your permissions and returns the result, for example the text of one document or a list of file names.
- The result becomes part of your conversation with the assistant and is handled under the terms of the assistant provider.
PaperOffice does not receive your chat history, your prompts or the assistant's answers. Only the tool call itself reaches the server: tool name, parameters, time and user. PaperOffice does not upload documents to the assistant provider on its own; the provider only receives what the assistant asked for.
Every tool call is logged with time, user and Credits. Administrators see the calls under API & Developer → API Usage.
Billing
Every tool call through the connector is billed in Credits, exactly like the corresponding API call. There is no separate connector subscription. Some status and health queries are not charged; details are in the API documentation. When Credits run out, calls are rejected with a clear message; nothing is deleted. More in the guide on billing and Credits: Billing and Credits in PaperOffice AI.
Revoke access
- In the assistant, remove or disconnect the PaperOffice connector. The assistant stops using it immediately; conversations that already contain PaperOffice results keep that text.
- In PaperOffice, open Account → API. Assistant connections appear in the token list with an MCP badge. Delete the token of that connection there.
- For Cursor, rotate or delete the token on the same page.
Revoking access does not delete any data.
Troubleshooting
- The sign-in window does not open: allow pop-ups for the assistant and try a private browser window. In Team or Enterprise plans, ask the administrator whether the connector is enabled.
- Connected, but no PaperOffice tools appear: enable the tools for the conversation, or start a new conversation.
- “Unauthorized” during a tool call: the connection was revoked or expired. Connect again. With a token, check that it is a user or group token.
- The assistant finds no documents: ask for the workspace list first. The connected user may not have access to the workspace you expect. Recently uploaded documents need a moment until processing has finished.
- Not enough Credits: top up in the PaperOffice app or enable auto-refill.
Still stuck? Open a support ticket with the assistant and plan, the exact message, the time with time zone and, if possible, a screenshot without personal data.
Recommendation for IT teams
- Domains to allow: mcp.paperoffice.ai, api.paperoffice.ai and app.paperoffice.ai. All traffic uses HTTPS; no inbound connection to your network is required.
- Start with a pilot: one workspace and read-only roles. Enable write roles per workspace after the pilot.
- Review the API usage regularly during the first weeks.
Frequently asked questions
- Do I have to install anything? No. The assistant connects to a URL.
- Can the assistant see all my documents? Only what your PaperOffice user may see.
- Does PaperOffice read my chats? No. Only the tool calls reach PaperOffice.
- Is there a separate subscription for the connector? No. Calls are billed in Credits like API calls.
- How do I end access? Remove the connector in the assistant and delete the token of the connection under Account → API.