MCP server exposing Galaxy UI components — manifests, source code, and framework coverage
Nebula MCP Server — exposes Galaxy UI components to AI assistants through the Model Context Protocol. Works with Claude Desktop, Cursor, Windsurf, Cline, and any MCP-compatible client.
| Tool | Description |
|---|---|
list_components | All components with per-framework availability (React, Vue, Angular, React Native, Flutter) |
get_component | Detailed manifest — props, files, dependencies, framework status |
get_component_source | Actual source code for a specific component file |
get_coverage | Coverage matrix across all 5 frameworks (67 components) |
search_components | Search by name or description |
All component data + 700 source files are bundled inside the package — zero setup, works offline.
npx -y @smithery/cli@latest install galaxy-stack/design-mcp --client claude
Add to your MCP client config:
{
"mcpServers": {
"galaxy-ui": {
"command": "npx",
"args": ["-y", "@galaxy-stack/nebula-mcp"]
}
}
}
~/Library/Application Support/Claude/claude_desktop_config.json~/.cursor/mcp.jsonPaste into clients that support remote MCP (Claude web Custom Connectors):
https://nebula-mcp--galaxy-stack.run.tools
"List Galaxy UI components for React"
"Show me the source code of the Vue Select component"
"Which components are missing in Flutter?"
Bump version in package.json
Push to main — GitHub Actions workflow publish-mcp.yml builds contracts artifacts, bundles data, verifies the version is new, and publishes via npm Trusted Publishing (OIDC) — no NPM_TOKEN required
Rebuild the MCPB bundle and run smithery mcp publish for Smithery
Publish to the Official MCP Registry (org namespace requires a PAT — device-flow login cannot read org roles, see registry#1468):
# PAT needs read:org scope (classic) or Organization → Members → Read-only (fine-grained)
mcp-publisher login github --token <YOUR_PAT> # requires mcp-publisher >= 1.8.1
mcp-publisher validate
mcp-publisher publish # → io.github.galaxy-nebula/nebula-mcp
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @galaxy-stack/nebula-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-galaxy-nebula-nebula-mcp": {
"command": "npx",
"args": [
"-y",
"@galaxy-stack/nebula-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/nebula-mcpnpmGalaxy Nebula 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.