2026-10-11 17:15 UTC

Google claims its Universal Search MCP Server developer preview lets agents search Gmail, Drive, Calendar, and Chat through one OAuth-scoped search_corpus tool, reducing the need for separate product-specific retrieval integrations.

state: seedheat: mediumuncertainty: mediumconvergesscott: mediumrag mcp workspace-searchGoogle

What is this?

Google’s developer documentation describes a Universal Search MCP Server for Workspace that lets AI agents search Gmail messages, Drive files, Calendar events, and Chat spaces and messages through a single tool, search_corpus. Users can grant only a subset of the requested OAuth scopes, and Google says the server searches only the products authorized by those grants. The case identifies it as a Developer Preview Program service, but the supplied web excerpt does not explicitly confirm that status for Universal Search itself; separate Google documentation lists product-specific Workspace MCP servers in developer preview. The single-tool interface supports the proposed reduction in separate search integrations, but the snippets do not establish retrieval quality or measured integration savings.

Why it matters to Scott

Google’s single cross-product search tool converges narrowly with Scott’s BI for Soft Data argument for replacing per-agent container integrations with one read surface, opening a concrete comparison between vendor-managed search and his compiled knowledge layer. It gives his RAG/Wiki Substrate Rule a new retrieval option to evaluate, not evidence that Google supplies compiled relationships or semantic containment; integration savings and retrieval quality remain unmeasured, and no supplied radar page tracks this exact development.
ip:framework.bi-for-soft-dataip:framework.rag-wiki-substrate-ruleradar:concept.googleradar:pipeshub-company-data-contextradar:microsoft-workiq-enterprise-contextradar:cloudflare-optional-oauth-scopes
queries asked of Scott's wikis
  • Cross-source retrieval federated search versus custom RAG pipelines
  • MCP tool consolidation agent harness integration overhead
  • Google Workspace connectors Gmail Drive Calendar Chat projects
  • OAuth least privilege permission-aware agent retrieval
  • Managed retrieval versus agent-maintained knowledge indexes

Measured heat

now 0 pts/hpeak 0 pts/hcomments 0/hpeers p14momentum: steady2 platformsage 474h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

09-21 22:35 (minted)⭐ origin echo-reconstructedDocuments a Developer Preview Program service with a single cross-product search tool, selective OAuth scopes, and configuration instruction
Google on blog (echo) · attributed from hn.story.49794043 · published time unknown
—
09-21 22:02first on hacker news · published · lag ?Let AI agents search across workspace with the Universal Search MCP Server
elpakal
—
09-21 22:02amplified on hacker news 👑hn.story.49794043
elpakal
peak 1 · 0 comments · 106% of case engagement
09-21 22:21our radar first saw it · lag ?discovery anchor: hn.story.49794043—
pace: p9 vs 1032 stories at the 336h mark (now 474h old) — behind addom-local-coding-harness (0.5x)

Evidence (2) — ⭐ canonical anchor

sourceobjectauthorscorecomments
🟧 hnLet AI agents search across workspace with the Universal Search MCP Server
Retrieved article excerpt

Open article · Retrieved 2026-09-21T22:23:16.200631+00:00

Send feedback

# Let AI agents search across workspace with the Universal Search MCP Server for Workspace Stay organized with collections Save and categorize content based on your preferences.



**Developer Preview:** Available as part of the
[Google Workspace Developer Preview Program](https://developers.google.com/workspace/preview),
which grants early access to certain features.

The Universal Search MCP Server for Google Workspace uses the
[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction)
standard to allow AI agents to search your Workspace artifacts. This server
provides a way to search across multiple Google Workspace products,
including Gmail messages, Google Drive files, Google Calendar
events, and Google Chat spaces and messages, using a single tool.

The Universal Search MCP Server provides a standardized way for AI agents to
search for information across your entire Google Workspace account without
needing to call individual product-specific tools.

## Prerequisites

- Membership in the
  [Google Workspace Developer Preview Program](https://developers.google.com/workspace/preview).
- A Google Cloud project. To create a project, see
  [Create a project](https://developers.google.com/workspace/guides/create-project).
- An MCP client, like [Google Antigravity](https://antigravity.google/).
- To run the commands on this page, set up the gcloud CLI in one of the
  following development environments:

  ### Cloud Shell

  To use an online terminal with the gcloud CLI already set up, activate
  Cloud Shell:

  [Activate Cloud Shell](https://console.cloud.google.com/home/dashboard?cloudshell=true)

  ### Local shell

  To use a local development environment, follow these steps:

  1. [Install the Google Cloud CLI](https://cloud.google.com/sdk/docs/install).
     If you installed the gcloud CLI previously, make sure you have the
     latest version by running `gcloud components update`.
  2. If you're using an external identity provider (IdP), sign in to the
     gcloud CLI with your federated identity. For more information, see
     [Sign in to the gcloud CLI with your federated identity](https://docs.cloud.google.com/iam/docs/workforce-log-in-gcloud).
  3. [Initialize the gcloud CLI](https://docs.cloud.google.com/sdk/docs/initializing).

## Configure the Universal Search MCP Server

To use the Universal Search MCP Server, you must enable it in your
Google Cloud project and then configure your MCP client to connect to it.

### Enable the APIs

To use the Universal Search MCP Server, enable the Google Workspace
MCP API and the APIs for the products that you want to search in your Google Cloud
project:

- Gmail API
- Google Drive API
- Google Calendar API
- Google Chat API
- Google Workspace MCP API

### CLI

```
gcloud services enable gmail.googleapis.com \
drive.googleapis.com \
calendar-json.googleapis.com \
chat.googleapis.com \
workspacemcp.googleapis.com --project=PROJECT_ID
```

Replace `PROJECT_ID` with your Google Cloud project ID.

### Console

Enable the APIs in the Google Cloud console:

[Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=gmail.googleapis.com,drive.googleapis.com,calendar-json.googleapis.com,chat.googleapis.com,workspacemcp.googleapis.com)

### Set up the OAuth consent screen

The Universal Search MCP Server uses OAuth 2.0 for authentication and authorization.
You must configure the OAuth consent screen before you can create an OAuth client ID.

If you have already configured the OAuth consent screen for other MCP servers,
ensure you have added the required scopes for the Universal Search MCP Server.

When you authenticate with the Universal Search MCP Server, you can choose to
authenticate all requested scopes or only a subset of them. The server respects
these choices and only searches across the products for which access has been
granted.

For example, if you authenticate with all of the following scopes:

- `https://www.googleapis.com/auth/gmail.readonly`
- `https://www.googleapis.com/auth/drive.readonly`
- `https://www.googleapis.com/auth/calendar.readonly`
- `https://www.googleapis.com/auth/chat.messages.readonly`

Universal Search MCP Server will search across Gmail, Google Drive,
Google Calendar, and Google Chat.

However, if you only grant access to
`https://www.googleapis.com/auth/drive.readonly`,
`https://www.googleapis.com/auth/calendar.readonly`,
and `https://www.googleapis.com/auth/chat.messages.readonly`
(and omit `https://www.googleapis.com/auth/gmail.readonly`), universal search
only returns results from Google Drive, Google Calendar, and Google Chat.
It doesn't search your email or return Gmail results.

1. In the Google Cloud console, go to **Google Auth Platform** **>** **Data Access**.
2. Click **Add or Remove Scopes**.
3. Add one or more of the following scopes:

   - `https://www.googleapis.com/auth/gmail.readonly`
   - `https://www.googleapis.com/auth/drive.readonly`
   - `https://www.googleapis.com/auth/calendar.readonly`
   - `https://www.googleapis.com/auth/chat.messages.readonly`
4. Click **Update** and then **Save**.

For detailed instructions on setting up the consent screen, see
[Configure the Google Workspace MCP servers](https://developers.google.com/workspace/guides/configure-mcp-servers#configure-consent-screen).

### Configure your MCP client

To add the Universal Search MCP Server to your MCP client, follow the
instructions for your client.

### Antigravity

To add the Universal Search MCP Server to Antigravity,
add the server configuration to your `mcp_config.json` file. These
instructions support Antigravity 2.0, Antigravity IDE, and Antigravity CLI.

1. Create an OAuth 2.0 client ID and secret of type **Web application**. In the
   **Authorized redirect URIs** section, click **+ Add URI**, and then add
   `https://antigravity.google/oauth-callback` in the **URIs** field. For
   instructions, see [Configure the Google Workspace MCP servers](https://developers.google.com/workspace/guides/configure-mcp-servers#configure-mcp-client).
2. Open or create the configuration file `~/.gemini/config/mcp_config.json`.
3. Add the `workspace-universal` configuration to `mcp_config.json`:

   ```
   {
     "mcpServers": {
       "workspace-universal": {
         "serverUrl": "https://workspacemcp.googleapis.com/mcp/v1",
         "oauth": {
           "clientId": "OAUTH_CLIENT_ID",
           "clientSecret": "OAUTH_CLIENT_SECRET"
         }
       }
     }
   }
   ```

   Replace the following:

   - `OAUTH_CLIENT_ID`: The client ID you created.
   - `OAUTH_CLIENT_SECRET`: The client secret you created.
4. Save `mcp_config.json`.
5. Authenticate the MCP server. You can authenticate using either the GUI settings or the CLI:

   - **For Antigravity IDE or GUI (Antigravity 2.0):**

     1. Open your settings screen (e.g., click **Settings** at the bottom-left or open **Antigravity User Settings**).
     2. Navigate to **Customizations**.
     3. Under **Installed MCP Servers**, click **Refresh**.
     4. Find `workspace-universal` in the list, click **Authenticate**, sign in to your Google Account, copy the authorization code, paste it into the input dialog, and click **Submit**.
   - **For Antigravity CLI:**

     1. Start Antigravity CLI:

        ```
        agy
        ```
     2. Open the interactive MCP management panel by running:

        ```
        /mcp
        ```
     3. Use the arrow keys to select `workspace-universal`, move to the **Authenticate** action, and press **Enter**. Complete the sign-in flow in your browser, copy the authorization code, paste it into the terminal prompt, and press **Enter**.
6. Verify that the server is correctly configured and running:

   - **For Antigravity IDE or GUI:** A **Sign out** button is displayed next to `workspace-universal` under **Customizations** > **Installed MCP Servers**.
   - **For Antigravity CLI:** Open the `/mcp` panel to view your configured MCP servers. Verified and authenticated servers display **Authed** next to their names inside the interactive TUI panel. You can select the `workspace-universal` server under the dashboard view to inspect its status and list all of its available tools.

### Claude

To add the Universal Search MCP Server to Claude, configure a custom
connector.

1. Create an OAuth 2.0 client ID and secret of type **Web application**. For
   instructions, see [Configure the Google Workspace MCP servers](https://developers.google.com/workspace/guides/configure-mcp-servers#claude).
2. In Claude settings, add a custom connector:

   - **Server name**: `Universal Search MCP Server`
   - **Remote MCP server URL**: `https://workspacemcp.googleapis.com/mcp/v1`
   - **OAuth client ID** and **OAuth client secret**: Enter your credentials.
   - **Scopes**: Include `https://www.googleapis.com/auth/gmail.readonly`, `https://www.googleapis.com/auth/drive.readonly`, `https://www.googleapis.com/auth/calendar.readonly`, and `https://www.googleapis.com/auth/chat.messages.readonly`.

## Test the Universal Search MCP Server

Try asking your MCP client questions that require searching across different
products:

- **"Find anything related to Project X across my email, docs, and chat messages."**
- **"When is my next meeting about the marketing plan, and what are the latest notes and chat messages on it?"**

If the tools execute successfully and you receive relevant responses from
multiple products, your Universal Search MCP Server is correctly configured.

## Supported tools

The Universal Search MCP Server offers the following tool:

- `search_corpus`: Performs a search across multiple Google Workspace
  products (Google Drive, Gmail, Google Calendar, and
  Google Chat) based on the provided query.






Send feedback
elpakal10
🟧 echo.blog ⭐Documents a Developer Preview Program service with a single cross-product search tool, selective OAuth scopes, and configuration instructionGoogle——

Interpretation history

Decision trace