mcp-toolkit
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 |
|---|---|
| generate_componentB | Generate a React component using actual shadcn/ui source code with TypeScript types, tests, and Storybook stories |
| list_templatesA | List all available shadcn/ui component templates |
| generate_component_libraryC | Generate multiple components at once using shadcn/ui templates |
| check_component_existsA | Check if a component already exists at the specified path |
| review_componentA | Review a generated component for TypeScript errors and accessibility issues. Returns a quality score and suggestions. |
| fix_componentA | Auto-fix common issues in a component: broken import paths, missing displayName, @/lib/utils → relative path |
| improve_componentA | Improve a component by expanding tests with edge cases, adding more Storybook story variants, and enhancing docs |
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 7 tools
Each tool has a distinct purpose: checking existence, fixing, generating single/library, improving, listing templates, and reviewing. No overlaps or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., check_component_exists, fix_component, generate_component.
7 tools is well-scoped for a component generation toolkit, covering the essential operations without bloat.
The tool set covers the full lifecycle: listing templates, generating, checking existence, fixing, improving, and reviewing. Gaps like deletion are not needed for this domain.