stacklok / stacklok/toolhive-studio

MCP servers listed in source order instead of alphabetical when aggregating registries

Open Beginner friendly
#1,956 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
167
Forks
24
Avg merge
11h 32m
Merged PRs (30d)
91

Description

Summary

When connecting the ToolHive UI 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.

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

  1. Connect ToolHive UI to a registry server that aggregates multiple registries (e.g., the demo sandbox registry)
  2. Observe the ordering of MCP servers in the list
  3. Note that servers are grouped by source rather than sorted alphabetically across all sources

🤖 Generated with Claude Code

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the ToolHive UI's MCP server list and reproduce the ordering with the demo sandbox registry or another registry server that aggregates multiple registries. Trace how aggregated results are ordered, then verify that the displayed list is sorted alphabetically across all source registries rather than grouped by source.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.