Support Ticket Template: Custom MCP Connector Session Binding Issue
Custom MCP Connector tool schemas fail to bind to new chat sessions unless toggled (disable/enable)
Priority: Medium/High (Blocks user onboarding and daily usability of custom integrations)
Issue Summary
We have created and registered a custom Model Context Protocol (MCP) connector in our Gemini Enterprise environment. However, the connector is not being identified or utilized by the model when starting a brand-new chat session.
Currently, the connector only becomes functional if we manually disable and re-enable the connector in the settings, and then refresh the active browser session. Only after performing this manual toggle sequence does Gemini Enterprise identify and utilize the custom MCP tools in the chat.
Expected Behavior
When a custom MCP connector is enabled globally, any newly initiated chat session should automatically detect, bind, and have immediate access to the connector’s registered tool schemas without requiring user toggling.
Actual Behavior
Upon starting a new chat, the model behaves as if the connector is not configured or fails to identify any of its tools. The runtime fails to bind the custom actions to the LLM context until a hard cache-invalidation is forced via a manual disable-then-enable toggle and browser refresh.
Technical Context & Observed Indicators
-
Connector Type: Custom MCP Connector.
-
Authentication Method: OAUTH
Steps to Reproduce
-
Ensure the custom MCP connector is in an Enabled state in the Gemini Enterprise Console.
-
Open Gemini Enterprise and click New Chat.
-
Ask a prompt that explicitly requires one of the custom MCP tools (e.g., “Retrieve the system status”).
-
Result: The model fails to identify the connector or state that the tool is available.
-
Go back to Connectors, Disable the connector, Enable it again.
-
refresh/reload the browser page, and re-submit the query.
-
Result: The model immediately identifies the connector and successfully executes the tool call.