# allxsmith/bestax [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/allxsmith/bestax/tree/main/bestax-mcp  
**GitHub Stars:** 14  
**npm Downloads (last month):** 14723  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/allxsmith-bestax

## Description
Gives agents props, examples and CSS variables for the Bestax React component library (Bulma v1). Runs offline.

## Tools
Capabilities this server exposes over MCP:

- **search_bestax** — Search components, props, usage examples, CSS variables and agent skills at once. The entry point — each hit names the tool to call for the full thing. Use this before guessing a component name.
- **list_components** — Every documented component with a one-line purpose, grouped by category. Cheap — use it to find the right name before calling get_component.
- **get_component** — Import statement, summary and prop table for one component. Add `include` for examples, CSS variables, accessibility notes or related components. A dot-path like "Navbar.Brand" answers with that part.
- **get_props** — The prop table for a component, or for one part of a compound family (pass a dot-path like "Navbar.Brand"). Cheaper than get_component when the props are all you need.
- **get_examples** — Working examples from the component's documentation page. Every one is executed on the docs site, so they compile against this version.
- **get_css_variables** — The --bulma-* custom properties a component reads, with their Sass names and defaults. This is how you restyle bestax — reach for these before writing custom CSS. Omit `component` to search across all of them.
- **get_helper_props** — The helper props every bestax component accepts — spacing, colour, typography, flexbox, visibility — and their valid values. Call this BEFORE writing an inline style or a utility class by hand; this library expects those to be props.
- **lookup_bulma_classes** — The bestax component and props for a Bulma class string, one row per class: "button is-primary", "columns is-mobile", "has-text-centered mt-4". Call this BEFORE writing a Bulma class by hand, and when converting existing Bulma markup. Pass the tag the classes sit on when there is one.
- **list_skills** — The bestax Agent Skills — task-level guides for forms, theming, layout scaffolding, icons, custom components, migration and CSS size. Read one with get_skill when a task matches.
- **get_skill** — A skill's instructions, or one of its reference documents. Load the skill first; pull a reference only when you need that depth.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "bestax": {
    "command": "npx",
    "args": ["-y","bestax-mcp@1"],
    "env": {
      "BESTAX_MCP_NO_VERSION_CHECK": "",
      "BESTAX_MCP_PROJECT_DIR": ""
    }
  }
}
```

**Requires environment variables:** `BESTAX_MCP_NO_VERSION_CHECK`, `BESTAX_MCP_PROJECT_DIR` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What allxsmith/bestax does

allxsmith/bestax exposes the documentation and implementation guidance for `@allxsmith/bestax-bulma`, a React component library based on Bulma v1. Its packaged index includes component purposes, imports, props, compound component paths such as `Navbar.Brand`, working TSX examples, accessibility details, related components, and the CSS custom properties used by components.

The server also includes the library’s seven Agent Skills: `custom-component`, `form`, `theming`, `layout-scaffold`, `icons`, `migrate`, and `optimize`. These can be accessed through MCP tools and resources alongside the component catalog.

## How it works

The catalog ships inside the npm package, so lookups run locally without network requests or rate limits. Begin with `list_components` when browsing by category, or use `search_bestax` when the component name is unknown. Follow the result with a focused lookup such as `get_component`, `get_props`, or `get_examples`.

At startup, the server looks for the installed `@allxsmith/bestax-bulma` package from its working directory and compares that version with the release represented by its index. This helps identify situations where an agent is consulting documentation for a different library version. The check can be skipped when needed.

## Setup and configuration

For Claude Code, register the server with `npx -y bestax-mcp@1`. Cursor, Claude Desktop, Windsurf, and Cline can use the same command and arguments in their MCP configuration. Pinning the major version keeps launches from automatically selecting an unrelated major release; projects can instead place the package in dev dependencies and let a lockfile control resolution.

The server normally checks the project represented by its working directory. Set `BESTAX_MCP_PROJECT_DIR` to an explicit project path when the client launches MCP processes elsewhere. Set `BESTAX_MCP_NO_VERSION_CHECK=1` to disable the installed-version check.

## Tools and capabilities

- `list_components` organizes every component by category with a short purpose.
- `search_bestax` ranks matches across components, props, examples, CSS variables, and skills.
- `get_component`, `get_props`, and `get_examples` provide component details, prop tables, and documented TSX samples.
- `get_css_variables` maps a component’s `--bulma-*` properties to Sass names and defaults.
- `get_helper_props` covers spacing, color, typography, flexbox, and visibility props for styling without inline CSS.
- `lookup_bulma_classes` maps Bulma class strings to Bestax components and props.
- `list_skills` and `get_skill` expose the library’s skill instructions and reference documents.

Resources include the catalog, component records, skills, and skill reference documents.

## Limitations and notes

The index describes one specific `bestax-bulma` release, so the version check matters when the application uses another release. The package is designed for local documentation lookup and does not require network access for its catalog. If no installed Bestax package is found, the server reports that condition in its initial response.

_Full upstream README: https://allmcps.com/mcp/allxsmith-bestax/readme_

