Align Toolhive CLI and UI on virtual registry usage
Open
Nobody has claimed this yet.
cli
documentation
enhancement
go
registry
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Update Toolhive so both the CLI and UI use the same virtual registry model as Cloud UI:
- Ensure both CLI and desktop app can discover and select virtual registries from a Registry endpoint (no direct reliance on sub-registries or the deprecated aggregated endpoint).
- Keep local experimentation workflows working (e.g., pointing directly to file/git-based data sources) while encouraging virtual registries as the primary way to expose MCP servers/skills.
- Remove/avoid any UX that assumes only a single registry per Toolhive instance if it conflicts with the virtual registry model.
- Document how users should configure Toolhive (CLI + UI) with virtual registries going forward
Related to https://github.com/stacklok/toolhive-registry-server/issues/464
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the CLI and desktop app currently discover registries, then compare those paths with the Registry endpoint and virtual registry model described here. Preserve direct file- and git-based experimentation, update CLI and UI configuration guidance, and consider the work done when both clients use virtual registries without assuming a single registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100