Skip to content

W-22059654-mcp-bridge-inmutability-fa #655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
failup merged 1 commit into from
May 19, 2026
+16 −0
Merged

W-22059654-mcp-bridge-inmutability-fa #655

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions modules/ROOT/pages/create-instance-task-mcp-bridge.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,8 @@ image:mcp-bridge-instance.png["The MCP Bridge instance is deployed on a gateway

NOTE: MCP Bridge doesn't support API instances with multiple upstream services.

IMPORTANT: MCP Bridge instances are immutable. After an MCP Bridge is deployed, you cannot add, remove, or modify its tools. To change the tool configuration, create a new MCP Bridge instance. See <<update-bridge>>.

[[add-server]]
== Add a New Agent or Tool Instance

Expand Down Expand Up @@ -76,6 +78,20 @@ To switch among API instances, select the name of the API.
. Review your selections and edit them if necessary.
. If you are ready to deploy, click *Save & Deploy*. Otherwise, select *Save* to deploy the instance later.

[[update-bridge]]
== Update an MCP Bridge

MCP Bridge instances are immutable by design. After deployment, you cannot modify the tool list or tool configuration of an existing MCP Bridge instance. This design ensures runtime stability and consistency in LLM-driven workflows, where agents rely on a fixed, predictable set of tools.

Allowing dynamic updates could cause synchronization issues: an agent might operate on a cached tool list while the underlying bridge definition has already changed, leading to unpredictable behavior. This is comparable to modifying an API contract (such as a RAML or WSDL definition) during an active transaction.

To update your MCP Bridge, create a new instance with the desired tool configuration:

. Follow the steps in <<add-server>> to create a new MCP Bridge with the updated set of tools.
. Update any agents or clients to point to the new MCP Bridge instance.
. Delete the previous MCP Bridge instance when it is no longer in use.


== See Also

* xref:latest-overview-concept.adoc[]
Expand Down