Props, examples, CSS variables and Agent Skills for bestax-bulma React components (Bulma v1)
The io.github.allxsmith/bestax-mcp MCP server provides “Props, examples, CSS variables and Agent Skills” for bestax-bulma React components, targeting Bulma v1. Its purpose is to supply component-related context and reusable references for developers working with these libraries.
🛠️ Key Features
Props for bestax-bulma React components
Examples
CSS variables
Agent Skills
Bulma v1 scope
🚀 Use Cases
Developing with bestax-bulma React components on Bulma v1
Referencing component props and usage examples
Using CSS variables associated with the component set
Integrating “Agent Skills” tied to these components
⚡ Developer Benefits
Centralized access to component props, examples, and CSS variables
Component-focused context for agent-related skills
⚠️ Limitations
Described functionality is limited to bestax-bulma React components and Bulma v1, as stated in the server description
It gives a coding agent the whole library: every component's props (including
compound sub-parts like Navbar.Brand), ~900 working examples, the --bulma-*
CSS variables behind every component, the helper props that replace inline
styles, and the bestax Agent Skills as
invocable prompts.
Offline and version-pinned. The index ships inside the package — no network
calls, nothing to rate-limit. It documents one specific bestax-bulma release,
and the server checks the version actually installed in your project and warns
you when they disagree, rather than confidently describing props you do not have.
Setup
Each release is published to the official
MCP Registry as
io.github.allxsmith/bestax-mcp, for clients that install from it.
The server checks your installed @allxsmith/bestax-bulma against the version it documents,
looking for it from the directory it starts in. If your client starts servers somewhere other than
your project, point it at the project with BESTAX_MCP_PROJECT_DIR in the config's env:
If it finds no installed copy, its first answer says so.
The @1 pins the major version. Without it, npx resolves whatever is newest on every
launch — so a breaking change, or a compromised release, reaches your agent the next time it
starts, with no review step. Add it to your dev dependencies instead if you would rather your
lockfile decide.
Tools
Start with list_components — its output names the tool to call next. Reach for
search_bestax when you need a component whose name you do not know.
Tool
What it gives you
list_components
Every component with a one-line purpose, by category
search_bestax
Components, props, examples, CSS variables and skills in one ranked list
get_component
Import, summary and props; optionally examples, CSS variables, accessibility, related
get_props
One prop table, including compound sub-paths (Navbar.Brand)
get_examples
Working tsx examples from the component's docs page
get_css_variables
The --bulma-* custom properties a component reads, with Sass names and defaults
get_helper_props
Spacing, colour, typography, flexbox and visibility props — call this before writing an inline style
lookup_bulma_classes
The bestax component and props for a Bulma class string (button is-primary), one row per class
list_skills
The seven bestax Agent Skills
get_skill
A skill's instructions, or one of its reference documents
Prompts
One per skill, so a task can start from the library's own guidance:
custom-component, form, theming, layout-scaffold, icons, migrate,
optimize.