This page explains how a team administrator can connect data sources using a custom Model Context Protocol (MCP) server, letting Gemini Enterprise – Business edition securely access your company's private data.
The custom MCP server connection lets you integrate private data, custom internal tools, and MCP-compliant third-party systems directly into the Gemini Enterprise – Business edition. This approach provides a unified method to connect internal and legacy systems when standard connectors are unavailable. With this integration, your AI agents can access business-critical information and specialized logic within your private infrastructure, maximizing the value of your existing technology investments.
For more information on building and deploying a custom MCP server, see Cloud Run MCP Server.
If you need additional assistance with design or implementation, consider partnering with a Google Cloud Partner.
For more information on enabling available connectors, see Connect your Google apps and third-party data.
Limitations
The custom MCP server has the following limitations:
- StreamableHTTP Only: The legacy
SSEtransport is not supported; only the new StreamableHTTP transport is compatible. - IdP public accessibility: Your Identity Provider (IdP) must be accessible from the public internet to perform the OAuth 2.0 handshake and retrieve authorization tokens.
- MCP server public accessibility: Your MCP server must be exposed to the public internet on a secure HTTPS endpoint to receive requests routed from Gemini Enterprise – Business edition.
Add a custom MCP server connection
To add a custom MCP server connection:
- Sign in to Gemini Enterprise – Business edition (business.gemini.google/).
- Click Settings & help
.
- Select your Team (for example, Jane Doe's Team), and then go to Manage team > Connected apps.
-
In the Connected apps page, click Add MCP Server. The Add MCP Server configuration page displays.
-
In the MCP info section, enter the following details:
Field Description MCP Server URL This is the endpoint where your MCP Server is hosted. It must be an HTTPS URL. Gemini Enterprise – Business edition only supports the StreamableHTTPtransport, and the URL often ends with/mcp—for example,https://mcp.example.com/mcp.Name Enter a name for the MCP data connector.
Description Enter a description that helps Gemini Enterprise – Business edition to understand what the server does and when to use it. For more information, see Write effective MCP Server descriptions and instructions.
-
In the Authentication settings section, enter values in the following required fields:
Field Description Authorization URL The base URL for the user to authorize Gemini Enterprise to access your MCP server. For example,
https://mcp.example.com/authorize/.Note: Enter only the base URL, without query parameters. Gemini Enterprise – Business edition automatically appends standard OAuth parameters (such asclient_id,redirect_uri, andscope) during authorization. If your authorization server requires additional parameters, specify them in the Authorization URL Parameters field.Token URL The endpoint is used for token exchange. For example,
https://mcp.example.com/token/.Authorization URL Parameters Optional. Any additional parameters required by your authorization URL. For example, to get a refresh token from a Google MCP server, enter
&access_type=offline&prompt=consent.
If your authorization server requires anaudienceparameter, you can add it as a parameter in this setting. For example,&audience=https://api.your-domain.com/v1/.Client ID The unique identifier of the OAuth app that you registered in your identity provider to represent Gemini Enterprise – Business edition. Client Secret The confidential key associated with the OAuth app that you registered in your identity provider to represent Gemini Enterprise – Business edition. Scopes The permissions that define what actions Gemini Enterprise is allowed to perform on behalf of a user, or what data it's allowed to access. The scopes are used to access the MCP server. Gemini Enterprise requests these scopes during user authorization. Ensure that your OAuth app is configured to use these scopes.
When you specify scopes, consider the following: Provide a space-separated list of scopes. For example, for Box, you provide:root_readwrite manage_managed_users manage_groups. Ensure the scopes provided are sufficient to let the user sign in and use the tools or actions enabled by the administrator; otherwise, the agent cannot access your app. A common scope isoffline_access, which lets the app request a refresh token. -
Click Add. Your new MCP server is created and appears on the Connectors page.
Delete a custom MCP server connection
To delete a custom MCP server connection:
-
Select the MCP server that you want to delete in the Connectors & MCP Server list.
-
Select
and click Delete. This permanently removes the configured data connection. You can add the details back and reconfigure later if needed.