Skip to main content
The previous Buds package-and-publish quickstart is temporarily hidden while the external UI architecture moves to the MCP Apps standard.

​
Current direction

  • Register an MCP App endpoint directly with BudsCollab; CLI deployment is not required.
  • Discover tools, resources, extensions, authentication, and UI capabilities through MCP.
  • Review least-privilege permissions before adding the app to an account or room.
  • Let Buds own persistent room, wall, canvas, sharing, and collaboration state.
  • Use Buds CLI only as optional local inspection, development, and validation tooling.
Existing package, CLI, and registry reference pages remain available for compatibility work, but they are intentionally absent from public navigation and should not be treated as the default external app path.