ReactBits MCP Server
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 ReactBits components with optional filtering |
| get_componentA | Get the source code for a specific ReactBits component |
| search_componentsB | Search for ReactBits components by name or description |
| get_component_demoA | Get usage example and demo code for a ReactBits component |
| list_categoriesA | List all available component categories |
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 clear, distinct purpose: retrieving source code, demo code, listing categories, listing components, and searching. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_component, list_categories). No naming style conflicts.
Five tools is well-scoped for a component library server, providing essential operations without unnecessary bloat.
The set covers all read operations expected for a component library: listing categories, components, retrieving source and demos, plus search. No obvious gaps.