Install Docuoria

Docuoria extracts the data from your PDFs with templates your organisation keeps. Add it to the application you already use; the application signs you in the first time it connects.

The connector

Every application that takes a remote MCP connector uses one address:

https://api.docuoria.com/mcp

Sign-in is OAuth. The first time the application connects, it opens the Docuoria sign-in, where you sign in with a one-time passcode sent to your email address. Nothing is pasted into the application. Your first sign-in creates a personal organisation with you as its owner; see Sign in.

AI platforms

Every platform that takes a custom MCP connector uses the same address and the same sign-in.

• claude.ai and Claude Desktop: in Settings > Connectors, choose Add custom connector, name it Docuoria, and enter the connector address. On Team or Enterprise, the organization owner adds the custom connector for the organization first, and each member then connects to it.
• Claude Cowork: the same steps as claude.ai: Settings > Connectors > Add custom connector, named Docuoria, with the connector address.
• ChatGPT: in Settings > Connectors (Apps in newer versions), open Advanced settings and turn on Developer mode, which allows custom connectors. Choose Create, name it Docuoria, enter the connector address, and choose OAuth for authentication. In a Team or Enterprise workspace, an admin turns on Developer mode.
• Microsoft Copilot Studio: in the agent, open Tools and choose Add a tool, then Model Context Protocol, then New tool. Enter Docuoria as the name, a one-line description, and the connector address as the server URL; choose OAuth 2.0 for authentication and add the tool to the agent.
• Any other platform: in its settings, find Connectors, Integrations or MCP servers, add a custom or remote server named Docuoria with the connector address, and sign in when the platform asks.

Allow the upload

When you attach a PDF in a chat, the AI uploads it to api.docuoria.com from its code execution sandbox. If the sandbox cannot reach api.docuoria.com, the AI relays the sentence for its platform:

• claude.ai and Claude Desktop: The sandbox could not reach api.docuoria.com. Ask the user to allow it in Claude: on Free, Pro, or Max, turn on Settings > Capabilities > Allow network egress; on Team or Enterprise, the organization owner adds api.docuoria.com under Organization settings > Capabilities > network egress to specific domains. Then run the script again.
• ChatGPT: The sandbox could not reach api.docuoria.com. Ask the user to allow it in ChatGPT: turn on Settings > Data controls > Work network access > Allow public internet access (a workspace admin sets it where the workspace restricts it). Then run the script again.
• Any other platform: The sandbox could not reach api.docuoria.com. Ask the user to allow network access to api.docuoria.com in the AI platform's code execution settings, then run the script again.

Developer tools

A developer tool can use the same connector: add https://api.docuoria.com/mcp as a remote MCP server in the tool's settings and sign in when it asks.

To keep documents on your machine, run Docuoria locally instead. Install the command line tool with dotnet tool install -g Docuoria.Cli (.NET 10 or later), then run one command in the project folder:

• Claude Code: docuoria init --tools claude
• Cursor: docuoria init --tools cursor
• VS Code with GitHub Copilot: docuoria init --tools github-copilot
• Codex: docuoria init --tools codex
• Windsurf: docuoria init --tools windsurf

docuoria init registers the local server (docuoria serve) in the tool's settings and records where templates live: your organisation's account by default, or the project folder with --store folder. The tool's settings name the installed docuoria executable by its full path, so after reinstalling the command line tool somewhere else, run docuoria init again. Then run docuoria login --service https://api.docuoria.com once to sign in on this machine; until you do, the local server keeps templates in the project folder. A project's settings never choose where a sign-in or a credential goes: docuoria login uses the service --service or DOCUORIA_SERVICE names, and the local server sends the machine's credential only to the service that issued it.

Automation platforms

Power Automate, n8n, and other flows call the REST routes with a connection key instead of a sign-in. An owner of the organisation creates the key on the Team page of the Docuoria account at https://www.docuoria.com/manage/team; a developer can also run docuoria account keys create --label "My flow", which signs the owner in with a device code, or call POST /connections with a label. The key starts with dk_, is shown once, and an owner can revoke it at any time on the same page. The flow sends it as Authorization: Bearer dk_... or as the bare key; either form works. The routes are described at https://api.docuoria.com/openapi.json.