[Bug]: Unable to create a new server with custom UUID

[MohanLaksh]

🐞 Bug Summary

While creating a new server with a custom UUID, the UUID of the server after creation is different from the one provided in the Custom UUID (optional) field. We are not getting the same UUID for the newly created server as input in the UUID field. However, we can edit and change the UUID for an already existing server.

🧩 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

1. make serve
2. "Add New Server" in the Virtual Servers Catlog tab using a pre-defined UUID in the Custom UUID (optional) field
3. The UUID of the server created will not match the pre-defined UUID in the Add New Server step. They both differ.

---

🤔 Expected Behavior

The new server created should have the same UUID as specified in the Custom UUID (optional) field while creating the server.

---

🧠 Environment Info

You can retrieve most of this from the /version endpoint.

Key	Value
Version or commit	v0.6.0 or main@/IBM/mcp-context-forge
Runtime	Python 3.12.3
Platform / OS	Ubuntu 22.04
Container	none

---

🧩 Additional Context (optional)

However, we can edit it to the UUID we want. Just that we cannot create with that name using the Custom UUID (optional) field