Skip to content
Google Document AI logo

Google Document AI MCP server

Extract text, entities, form fields and tables from documents with Google Document AI processors.

Google Document AI is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
Custom auth or OAuth 2.0
License
MIT, open source
Updated
October 2026

About the Google Document AI MCP server

Connect Google Document AI once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Google Document AI and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Google Document AI tools your AI can run

Once connected, your assistant can call any of these Google Document AI actions by asking in plain language.

  • Process Document

    Run a document through a Document AI processor and get its text, entities, form fields and tables

    10 fields

  • Custom API Call

    Call any Document AI endpoint. Paths start with the version, for example `/v1/projects/{project}/locations/{location}/processors`.

    10 fields

Give your assistant Google Document AI

Connect Google Document AI once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Google Document AI MCP, answered.

No. That is the point of it. One Activepieces server exposes Google Document AI alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Google Document AI in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Process Document, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.