Skip to content

fix(ui): clarify MCP Servers and Virtual Servers naming in admin UI#3988

Closed
kimsehwan96 wants to merge 1 commit intoIBM:mainfrom
kimsehwan96:fix/ui-naming-clarity
Closed

fix(ui): clarify MCP Servers and Virtual Servers naming in admin UI#3988
kimsehwan96 wants to merge 1 commit intoIBM:mainfrom
kimsehwan96:fix/ui-naming-clarity

Conversation

@kimsehwan96
Copy link
Copy Markdown
Contributor

🔗 Related Issue

N/A


📝 Summary

Clarify the Admin UI tab headers to reduce naming confusion between MCP Servers and Virtual Servers.

  • "MCP Servers & Federated Gateways (MCP Registry)" → "MCP Servers (Registry)"
  • "Virtual MCP Servers" → "Virtual Servers (Federated MCP Endpoints)"

The "Federated Gateways" label was misleading on the MCP Servers tab — federation is what Virtual Servers do (combining tools/resources from multiple MCP servers into a single endpoint), not what the MCP Servers registry does.


🏷️ Type of Change

  • Bug fix
  • Feature / Enhancement
  • Documentation
  • Refactor
  • Chore (deps, CI, tooling)
  • Other (describe below)

Admin UI changes.


🧪 Verification

Check Command Status
Lint suite make lint pass
Unit tests make test pass
Coverage ≥ 80% make coverage pass

✅ Checklist

  • Code formatted (make black isort pre-commit)
  • Tests added/updated for changes
  • Documentation updated (if applicable)
  • No secrets or credentials committed

📓 Notes (optional)

UI-only text change, 2 lines modified in admin.html. No logic or behavior changes.

- MCP Servers tab: "MCP Servers & Federated Gateways (MCP Registry)"
  → "MCP Servers (Registry)"

- Virtual Servers tab: "Virtual MCP Servers"
  → "Virtual Servers (Federated MCP Endpoints)"

Signed-off-by: kimsehwan96 <sktpghks138@gmail.com>
@gcgoncalves
Copy link
Copy Markdown
Collaborator

Hi, @kimsehwan96, thanks for your pull request! Although I agree that the terminology is somewhat confusing, I do not agree with the proposed solution, as it goes too vebose and quite wide on the UI. Maybe a naming refactor might be discussed in the community, what do you think of opening a discussion about it?

@a-effort a-effort closed this Apr 15, 2026
@a-effort
Copy link
Copy Markdown
Collaborator

Appreciate your feedback; thank you for contributing! We're currently redesigning the UI and will address naming as part of that broader initiative.

@kimsehwan96
Copy link
Copy Markdown
Contributor Author

Thanks @gcgoncalves @a-effort — agreed, happy to close. Just wanted to ping the issue with this PR; the naming refactor is better left to maintainers/collaborators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants