Feature Request: Allow Multiple MCP Gateway Registrations with the Same Gateway URL #1392
Description
Description:
Currently, MCP Context Forge enforces a unique constraint on gateway_url within a team. This prevents creating multiple MCP Gateway configurations pointing to the same MCP URL, even when different credentials/different gateway names are provided.
Use Case (WXO Integration):
In the WXO scenario, multiple tenants (or users) may need to connect to the same MCP server endpoint (gateway_url) using different credentials. Each connection should be treated as an independent registration to enable proper credential scoping and isolation.The current uniqueness rule blocks this valid use case.
Proposed Change:
Relax the existing uniqueness constraint on gateway_url.
Instead, enforce uniqueness on the combination of (gateway_url + name).
This allows multiple gateways to reference the same MCP server, while still preventing accidental duplicates with identical names.
Expected Outcome:
Supports multi-tenant connections to a common MCP server while maintaining clear and manageable gateway entries. Ensures backward compatibility and minimal schema changes.