MCP Server

DocuTray runs a remote Model Context Protocol (MCP) server. Connect it to your AI assistant and the assistant can list your document types, extract structured data from PDFs and images, check the status of a conversion, validate extracted data, search your knowledge bases and report your monthly usage — all on behalf of your DocuTray organization, without copying an API key into the conversation.

https://app.docutray.com/api/mcp

What you need

• A DocuTray account. Create one if you don't have it yet.
• Membership in at least one organization. When you connect, you choose which organization the assistant works with.
• An MCP client that supports remote servers over Streamable HTTP with OAuth: Claude, Claude Code, ChatGPT, Cursor, VS Code (GitHub Copilot) or Copilot Studio, among others.

There is no API key to paste. The client signs you in with OAuth: you log in to DocuTray, pick the organization and approve the permissions it asks for.

Quick start

Claude Code

claude mcp add --transport http docutray https://app.docutray.com/api/mcp

Then run /mcp inside Claude Code, select docutray and complete the sign-in in your browser.

Cursor

The button opens Cursor and adds the server. Cursor then asks you to sign in.

Claude, ChatGPT, VS Code and Copilot Studio

See Connect a client for step-by-step instructions for every client.

Try it

Once connected, ask your assistant things like:

• "List my DocuTray document types."
• "Extract the data from this invoice with my invoice document type: https://example.com/invoice.pdf"
• "How many pages has my organization processed this month?"

More examples, and what each tool does, are in Tools.

How it works

AI client ──OAuth 2.1 + PKCE──▶ app.docutray.com/api/auth   (sign in, pick organization, consent)
    │
    └──Bearer access token────▶ app.docutray.com/api/mcp    (tools/list, tools/call)

• Authorization. The server follows the MCP authorization spec: it publishes OAuth Protected Resource Metadata at /.well-known/oauth-protected-resource/api/mcp, and clients register themselves through Client ID Metadata Documents or Dynamic Client Registration.
• One organization per connection. The organization you pick on the consent screen travels inside the access token. Tools always run against that organization; to work with another one, connect again and pick it.
• Same rules as the REST API. Conversions started through MCP use the same document types, consume the same monthly page quota and are subject to the same per-minute rate limit as the REST API. Each one is recorded in your organization's conversion log together with the MCP client that started it.

Learn more