🧭 Type of Feature

Once we create a "[Gateways/MCP Servers]", under the auto discovered Global Tools/Resources/Prompts, currently it is very difficult to identify the tools from which MCP Server/Gateway. Only way to identify is using URL as shown in the below attachment.
It will be better if you can have a column "Gateway/Server Name" under Global Tools/Resources/Prompts table which maps to the [Gateways/MCP Servers] Tab.

Please select the most appropriate category:

• [*] Enhancement to existing functionality
• New feature or capability
• New MCP-compliant server
• New component or integration
• Developer tooling or test improvement
• Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)
• Other (please describe below)

🧭 Epic

Title:
Goal: What is the big-picture objective of this feature set?
Why now: Why is this needed? Who benefits?

🙋♂️ User Story 1

As a:
I want:
So that: <some reason / value>

✅ Acceptance Criteria

Scenario: First scenario title
  Given some starting state
  When an action occurs
  Then a result should happen

Scenario: Second scenario title
  Given another state
  When something else happens
  Then another result occurs

🙋♂️ User Story 2

As a:
I want:
So that:

✅ Acceptance Criteria

Scenario: Third scenario title
  Given a specific setup
  When a user performs an action
  Then something meaningful happens

📐 Design Sketch (optional)

Include a diagram, sketch, or flow (use Mermaid if desired):

flowchart TD
    A[Client] -->|POST /completions| B(MCPGateway)
    B --> C[Completion Service]

🔗 MCP Standards Check

• Change adheres to current MCP specifications
• No breaking changes to existing MCP-compliant integrations
• If deviations exist, please describe them below:

🔄 Alternatives Considered

List any alternative designs, existing workarounds, or rejected ideas.

📓 Additional Context

Include related issues, links to discussions, issues, etc.