Skip to content
Book a demo Start building
Google Search logo

Google Search MCP server

Search using Vertex AI Search (Discovery Engine)

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

Start building See the Google Search integration
Tools
1
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
August 2026

About the Google Search MCP server

Connect Google Search 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 Search and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Google Search tools your AI can run

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

  • Search

    Search for content using Vertex AI Search (searchLite).

    2 fields

Google Search MCP, answered.

No. That is the point of it. One Activepieces server exposes Google Search 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 Search 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 1 tool, including Search, 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.