Chakra UI
Look up Chakra UI components, their props and examples, and review code against the current major version. No key required.
What Chakra UI exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the chakra-ui__ namespace. Your agent never loads them all — it searches, and gets the few that match.
chakra-ui__customize_theme1 argument · 1 required
Used to setup a custom theme for your Chakra UI. You can define new tokens or modify existing ones.
Required
categorychakra-ui__get_component_example1 argument · 1 required
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.
Required
componentchakra-ui__get_component_props1 argument · 1 required
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.
Required
componentchakra-ui__get_themeno arguments
Retrieve the theme specification (colors, fonts, textStyles, etc.) to design any page, component or section
chakra-ui__list_componentsno arguments
List all available components in Chakra UI. This tool retrieves the names of all available Chakra UI components.
chakra-ui__v2_to_v3_code_review1 argument · 1 required
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.
Required
scenario
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Chakra UI is already on
It needs no credential, so it is on for every account from the first call.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
