nebula-mcp
README.md
# @galaxy-stack/nebula-mcp
[](https://www.npmjs.com/package/@galaxy-stack/nebula-mcp)
[](https://www.npmjs.com/package/@galaxy-stack/nebula-mcp)
[](LICENSE)
**Nebula MCP Server** — exposes [Galaxy UI](https://galaxy-design.vercel.app) components to AI assistants through the [Model Context Protocol](https://modelcontextprotocol.io). Works with Claude Desktop, Cursor, Windsurf, Cline, and any MCP-compatible client.
## Tools
| 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.
## Install
### Smithery (recommended)
```bash
npx -y @smithery/cli@latest install galaxy-stack/design-mcp --client claude
```
### npx (manual)
Add to your MCP client config:
```json
{
"mcpServers": {
"galaxy-ui": {
"command": "npx",
"args": ["-y", "@galaxy-stack/nebula-mcp"]
}
}
}
```
- **Claude Desktop**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Cursor**: `~/.cursor/mcp.json`
### Remote endpoint
Paste into clients that support remote MCP (Claude web Custom Connectors):
```
https://nebula-mcp--galaxy-stack.run.tools
```
## Try it
> "List Galaxy UI components for React"
> "Show me the source code of the Vue Select component"
> "Which components are missing in Flutter?"
## Registries
- **npm**: [@galaxy-stack/nebula-mcp](https://www.npmjs.com/package/@galaxy-stack/nebula-mcp)
- **Smithery**: [smithery.ai/servers/galaxy-stack/nebula-mcp](https://smithery.ai/servers/galaxy-stack/nebula-mcp)
- **Official MCP Registry**: [io.github.galaxy-nebula/nebula-mcp](https://registry.modelcontextprotocol.io)
## Publishing (maintainers)
1. Bump `version` in `package.json`
2. 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
3. Rebuild the MCPB bundle and run `smithery mcp publish` for Smithery
## License
MIT © [Bùi Trọng Hiếu (kevinbui)](https://github.com/buikevin)
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: listing all, getting metadata, reading source, coverage statistics, and searching. There is no ambiguity between them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (list_, get_, get_, get_, search_) with clear resource names, making them predictable and easy to distinguish.
Tool Count5/5
With 5 tools, the set is well-scoped for a component registry server, providing exactly the necessary operations without unnecessary bloat or gaps.
Completeness5/5
The read-only surface covers all core needs: listing, detailed metadata, source retrieval, coverage reporting, and search. There are no obvious missing operations for this domain.