gluestack-ui-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (debug, info, warn, error). | info |
| GITHUB_TOKEN | No | GitHub Personal Access Token for API access. | |
| GLUESTACK_PATH | No | Path to local Gluestack UI installation. |
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 Gluestack UI components with their variants and features |
| get_componentB | Get the source code for a specific Gluestack UI component |
| get_component_demoB | Get demo code illustrating how a Gluestack UI component should be used |
| get_component_metadataB | Get metadata for a specific Gluestack UI component including props, dependencies, and examples |
| list_component_variantsA | List all available variants (nativewind, themed, unstyled) for a specific Gluestack UI component |
| get_directory_structureB | Get the directory structure of the Gluestack UI repository or a specific path within it |
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 6 tools
Each tool targets a distinct aspect: source code, demo, metadata, directory structure, list of components, and variants. No two tools overlap in purpose.
All tool names use a consistent verb_noun pattern with lowercase underscores (e.g., get_component, list_components). Perfectly predictable.
With 6 tools, the server covers the necessary operations without bloat. It is well-scoped for retrieving component information.
The tool set covers retrieval of component source, demo, metadata, variants, and directory structure. A minor gap might be a search or filter tool, but core needs are met.