The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Galaxy Nebula MCP Server listing page.
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.
Add to your MCP client config:
~/Library/Application Support/Claude/claude_desktop_config.json~/.cursor/mcp.jsonPaste into clients that support remote MCP (Claude web Custom Connectors):
"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):