@chakra-ui/react-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 2 of 2 tools tried
Contacts while installing and starting: chakra-ui.com
What it contacted
chakra-ui.com
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @chakra-ui/react-mcp@2.1.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 2 returned a result.
get_theme | Returned a result under 0.1 s · 4,835 characters |
list_components | Returned a result under 0.1 s · 1,972 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
v2_to_v3_code_review:ALWAYS use this tool to review any generated code. This tool helps you get familiar with the new Chakra UI
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_theme
Retrieve the theme specification (colors, fonts, textStyles, etc.) to design any page, component or section
v2_to_v3_code_review scenario
ALWAYS use this tool to review any generated code. This tool helps you get familiar with the new Chakra UI v3 API before/after code snippets for common migration scenarios to help avoid AI hallucination.
installation framework
Get lightweight installation steps for Chakra UI when using Vite, Next.js App Router, Next.js Pages Router, or general setup.
get_component_example component
Retrieve comprehensive example code and usage patterns for a specific Chakra UI component. This tool provides practical implementation examples including basic usage, advanced configurations, and common use cases with complete code snippets.
get_component_props component
Get detailed properties of a specific Chakra UI component. This tool retrieves the properties, attributes, design related props for a component, like size, variant, etc. and configuration options available for a given Chakra UI component.
customize_theme category
Used to setup a custom theme for your Chakra UI. You can define new tokens or modify existing ones.
list_components
List all available components in Chakra UI. This tool retrieves the names of all available Chakra UI components.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | github.com/chakra-ui/chakra-ui |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-WzsojxSX4AC+s9oMGGXHJozvrAmq+/BbsXKyhkg3CC4zCdGszUYZdA1tWJaoMAJ+TNSk4bfUcNHOfuFKMqX39g== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40chakra-ui/react-mcp)
New version out? Ask for a fresh report.