Summary
When connecting to a registry server that aggregates multiple registries, the MCP servers are not listed in pure alphabetical order. Instead, they are listed in source order first, then alphabetical within each source. This produces a confusing ordering for users who expect a single unified alphabetical list.
Same issue as stacklok/toolhive-studio#1956.
Expected behavior
MCP servers should be listed in alphabetical order regardless of which underlying registry they originate from.
Actual behavior
Servers are grouped by their source registry, with alphabetical ordering only applied within each group. This means you get clusters of servers from one registry followed by clusters from another, rather than a single sorted list.
Steps to reproduce
- Connect to a registry server that aggregates multiple registries (e.g., the demo sandbox registry)
- Observe the ordering of MCP servers in the list
- Note that servers are grouped by source rather than sorted alphabetically across all sources
🤖 Generated with Claude Code
Summary
When connecting to a registry server that aggregates multiple registries, the MCP servers are not listed in pure alphabetical order. Instead, they are listed in source order first, then alphabetical within each source. This produces a confusing ordering for users who expect a single unified alphabetical list.
Same issue as stacklok/toolhive-studio#1956.
Expected behavior
MCP servers should be listed in alphabetical order regardless of which underlying registry they originate from.
Actual behavior
Servers are grouped by their source registry, with alphabetical ordering only applied within each group. This means you get clusters of servers from one registry followed by clusters from another, rather than a single sorted list.
Steps to reproduce
🤖 Generated with Claude Code