MCP server exposing Galaxy UI components — manifests, source code, and framework coverage
This repository is the source workspace for Galaxy UI component packages and shared implementations.
It is not the same thing as the published CLI package. The copy-paste product surface lives in galaxy-design-cli, where users run init and add to fetch component source from GitHub and scaffold editable files into their apps.
This workspace currently contains:
@galaxy-ui/source export conditionIt does not currently contain standalone published packages for Next.js or Nuxt.js.
nextjs is a CLI/runtime target that maps to the React source packagenuxtjs is a CLI/runtime target that maps to the Vue source packageKey packages under packages/:
@galaxy-ui/react@galaxy-ui/vue@galaxy-ui/angularWhen the CLI reports support for Next.js or Nuxt.js, that support comes from framework-specific transforms on top of the React or Vue package sources in this workspace.
The root workspace uses Bun workspaces:
bun install
@galaxy-ui/react is currently the most publish-ready package in this workspace.
packages/react/src/index.tsnpm run build and npm pack --dry-run@galaxy-ui/vue now has a real library build pipeline.
packages/vue/src/index.tsvite build && vue-tsc -p tsconfig.build.jsondist/* artifacts@galaxy-ui/angular now has a real Angular library build pipeline.
packages/angular/src/index.tsng build galaxy-ui-angulardist/buikevin/galaxy-design repositoryDo not treat this repository as locked to Tailwind CSS v3.
From the repository root:
bun install
npm run lint
npm run test
Package-specific examples:
cd packages/react && npm run build
cd packages/react && npm pack --dry-run
cd packages/vue && npm run build
cd packages/angular && npm run build
Use this rule of thumb when working in this repo:
dist/index.js, dist/index.d.ts, or equivalent Angular output, the workspace must be able to build and pack those filesThe copy-paste user experience lives in galaxy-design-cli, not in this repository root.
That means:
init and add behavior should be documented where the CLI is published@galaxy-ui/react build and pack verification greenhttps://galaxy-design.vercel.apphttps://github.com/buikevin/galaxy-designhttps://github.com/buikevin/galaxy-design/issuesSource-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @galaxy-stack/design-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-buikevin-galaxy-design-mcp": {
"command": "npx",
"args": [
"-y",
"@galaxy-stack/design-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@galaxy-stack/design-mcpnpmGalaxy UI MCP Server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.