Galaxy Nebula MCP Server

io.github.galaxy-nebulaPublished by GitHub account galaxy-nebulav1.0.2Updated Oct 24, 2026

MCP server exposing Galaxy UI components — manifests, source code, and framework coverage

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant browse Galaxy UI component manifests, source files, and framework coverage for React, Vue, Angular, React Native, and Flutter.

What you can do
Exposes a bundled catalog of Galaxy UI components through five tools: list_components shows every component with per-framework availability, get_component returns a detailed manifest with props, files, dependencies, and framework status, get_component_source returns the source code of a specific component file, get_coverage returns a coverage matrix across all five frameworks, and search_components finds components by name or description. All component data and roughly 700 source files ship inside the package, so it works offline with no setup.
When to use it
Useful when an assistant needs to look up Galaxy UI component APIs, inspect component source, or check which components exist in a given framework while building or reviewing a UI. It is aimed at developers working with the Galaxy UI library rather than general coding tasks.
Requirements
Runs as a local stdio process, typically launched with npx from the npm package @galaxy-stack/nebula-mcp, so Node.js and npx are needed. The README also lists a remote endpoint for clients that support remote MCP. No authentication, environment variables, or headers are declared, and the bundled data means no network access is required for local use.
Before you install
The README's maintainer publishing section mentions a GitHub personal access token with read:org scope for registry publishing; that token is for maintainers and is not part of normal use. The server is read-only, exposing component data and source code, so it does not write, send, or delete anything. The README also suggests installing through a third-party CLI, which runs code from that package.

Installation

In SourceWeft

  1. Open Galaxy Nebula MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@galaxy-stack/nebula-mcp

[npm version] [npm downloads] [License: MIT]

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.

Tools

ToolDescription
list_componentsAll components with per-framework availability (React, Vue, Angular, React Native, Flutter)
get_componentDetailed manifest — props, files, dependencies, framework status
get_component_sourceActual source code for a specific component file
get_coverageCoverage matrix across all 5 frameworks (67 components)
search_componentsSearch 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

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

  4. Publish to the Official MCP Registry (org namespace requires a PAT — device-flow login cannot read org roles, see registry#1468):

    sh
    # 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.1mcp-publisher validatemcp-publisher publish                            # → io.github.galaxy-nebula/nebula-mcp

License

MIT © Bùi Trọng Hiếu (kevinbui)

Source: README.md at commit 3373958

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v1.0.2LatestSep 22, 2026
  2. v1.0.1Sep 21, 2026
  3. v1.0.0Sep 21, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.