[Bug]: Existing tool configurations are not updating after changes to the MCP server configuration. #834
Description
🐞 Bug Summary
When an existing gateway/mcp server is edited such as changes to URL, headers, transport type, etc. these updates should automatically propagate to all associated tools. However, the tools are currently not reflecting the updated gateway/mcp server parameters.
🧩 Affected Component
Select the area of the project impacted:
-
mcpgateway- API -
mcpgateway- UI (admin panel) -
mcpgateway.wrapper- stdio wrapper - Federation or Transports
- CLI, Makefiles, or shell scripts
- Container setup (Docker/Podman/Compose)
- Other (explain below)
🔁 Steps to Reproduce
- Add an MCP server with associated tools in the gateway.
- Change the server's protocol (e.g., from SSE to Streamable HTTP).
- Edit the server URL in the gateway configuration.
Observed Behavior: The tools' URLs do not update accordingly and still reflect the old server URL.
Note: Similar behavior is observed when modifying headers, authentication settings, or transport type—associated tool configurations do not reflect the changes.
🤔 Expected Behavior
When a gateway/mcp server is updated (e.g., changes to URL, headers, transport type, authentication, etc.), all tools linked to that gateway should automatically reflect the updated configuration. This ensures consistency and prevents mismatches between gateway settings and the tools that rely on them.
📓 Logs / Error Output
🧠 Environment Info
You can retrieve most of this from the /version endpoint.
| Key | Value |
|---|---|
| Version or commit | e.g. v0.9.0 or main@a1b2c3d |
| Runtime | e.g. Python 3.11, Gunicorn |
| Platform / OS | e.g. Ubuntu 22.04, macOS |
| Container | e.g. Docker, Podman, none |