Please select the area the issue is related to
Area/LLM & MCP Governance (LLM providers, LLM proxy, MCP proxy, provider keys)
Please select the aspect the issue is related to
Aspect/LLM & MCP (LLM providers, LLM proxy, provider keys, MCP proxy)
Description
An agent fails to promote across environments because its connection to an Model Context Protocol (MCP) tool gets permanently stuck in an "unbound" state. When attempting to promote the agent, the system blocks the action and reports that the MCP connection isn't bound in the target environment.
This error creates confusion because checking the MCP proxy configuration directly shows that it is properly bound to the target environment. The issue occurs when an MCP connection is attached to an agent before the proxy has an endpoint set up in that environment. While the UI reflects the updated proxy binding, the underlying agent mapping table never receives the update. The promotion check relies on this missing mapping row, sees an empty configuration, and rejects the deployment.
Because the system only attempts to sync these mappings during specific proxy update events, adding gateways or updating endpoints later fails to trigger a automatic repair for existing agents. As a result, agents created during this window remain stuck until someone manually disconnects and reconnects the MCP tool from the agent profile.
Steps to Reproduce
mentioned
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
No response
Please select the area the issue is related to
Area/LLM & MCP Governance (LLM providers, LLM proxy, MCP proxy, provider keys)
Please select the aspect the issue is related to
Aspect/LLM & MCP (LLM providers, LLM proxy, provider keys, MCP proxy)
Description
An agent fails to promote across environments because its connection to an Model Context Protocol (MCP) tool gets permanently stuck in an "unbound" state. When attempting to promote the agent, the system blocks the action and reports that the MCP connection isn't bound in the target environment.
This error creates confusion because checking the MCP proxy configuration directly shows that it is properly bound to the target environment. The issue occurs when an MCP connection is attached to an agent before the proxy has an endpoint set up in that environment. While the UI reflects the updated proxy binding, the underlying agent mapping table never receives the update. The promotion check relies on this missing mapping row, sees an empty configuration, and rejects the deployment.
Because the system only attempts to sync these mappings during specific proxy update events, adding gateways or updating endpoints later fails to trigger a automatic repair for existing agents. As a result, agents created during this window remain stuck until someone manually disconnects and reconnects the MCP tool from the agent profile.
Steps to Reproduce
mentioned
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
No response