nebula-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | List all available Galaxy UI components with their availability per framework |
| get_componentA | Get detailed metadata for a specific component including props, files, and per-framework status |
| get_component_sourceC | Read the source code of a specific component file |
| get_coverageA | Get component availability coverage across all frameworks |
| search_componentsB | Search components by name or description |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing all, getting metadata, reading source, coverage statistics, and searching. There is no ambiguity between them.
All tools follow a consistent verb_noun pattern (list_, get_, get_, get_, search_) with clear resource names, making them predictable and easy to distinguish.
With 5 tools, the set is well-scoped for a component registry server, providing exactly the necessary operations without unnecessary bloat or gaps.
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.