Current state
The registry currently models UI libraries with category, stack, use-case, and tag fields. It has no resource type, MCP transport/auth metadata, connector compatibility, or setup configuration.
Scope
- Define how libraries, MCP servers, and connectors coexist in the catalog before changing the schema.
- Add the minimum metadata needed for discovery and setup: resource type, provider, supported clients, transport/auth requirements, official docs/repository, and install or connection instructions.
- Make MCP servers and connectors searchable and filterable without weakening the existing library directory.
- Surface them on dedicated detail pages with a copyable client/agent setup prompt.
- Mark official versus community integrations and link claims to primary sources.
- Never store credentials; examples must use environment-variable placeholders.
- Seed a small set of verified entries to validate the model and UI.
Acceptance criteria
- Users can distinguish and filter libraries, MCP servers, and connectors.
- Each added integration has verified official links, compatibility information, and safe setup instructions.
- Secret values are neither requested nor committed.
- Existing library entries and filters remain valid.
No priority is implied by the issue number.