Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Props, examples, CSS variables and Agent Skills for bestax-bulma React components (Bulma v1)
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
BESTAX_MCP_NO_VERSION_CHECK, BESTAX_MCP_PROJECT_DIRYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"bestax": {
"command": "npx",
"args": [
"-y",
"bestax-mcp"
],
"env": {
"BESTAX_MCP_NO_VERSION_CHECK": "your-value",
"BESTAX_MCP_PROJECT_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add bestax --env BESTAX_MCP_NO_VERSION_CHECK=your-value --env BESTAX_MCP_PROJECT_DIR=your-value -- npx -y bestax-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"bestax": {
"command": "npx",
"args": [
"-y",
"bestax-mcp"
],
"env": {
"BESTAX_MCP_NO_VERSION_CHECK": "your-value",
"BESTAX_MCP_PROJECT_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"bestax": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bestax-mcp"
],
"env": {
"BESTAX_MCP_NO_VERSION_CHECK": "your-value",
"BESTAX_MCP_PROJECT_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
BESTAX_MCP_NO_VERSION_CHECK envBESTAX_MCP_PROJECT_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account allxsmith, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.18.33) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, aamio rendezvous
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The official MCP server for @allxsmith/bestax-bulma — React components for Bulma v1.
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.
Each release is published to the official MCP Registry as io.github.allxsmith/bestax-mcp, for clients that install from it.
claude mcp add bestax -- npx -y bestax-mcp@1
Or install the bestax plugin instead. It runs this same server and adds the bestax Agent Skills:
/plugin marketplace add allxsmith/bestax-skills
/plugin install bestax@bestax
Add to your MCP config (.cursor/mcp.json, claude_desktop_config.json, …):
{
"mcpServers": { "bestax": { "command": "npx", "args": ["-y", "bestax-mcp@1"] } } }
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:
{
"mcpServers": { "bestax": { "command": "npx", "args": ["-y", "bestax-mcp@1"], "env": { "BESTAX_MCP_PROJECT_DIR": "/path/to/your/project" } } } }
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.
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 |
One per skill, so a task can start from the library's own guidance: custom-component, form, theming, layout-scaffold, icons, migrate, optimize.
bestax://catalog · bestax://components/{name} · bestax://skills/{name} · bestax://skills/{name}/references/{ref}
| Variable | Effect |
|---|---|
BESTAX_MCP_NO_VERSION_CHECK | Set to 1 to skip the installed-version check entirely |
BESTAX_MCP_PROJECT_DIR | Your project's path, for a client that starts the server outside it; defaults to the working directory |
llms.txt and the Agent SkillsSource code licensed MIT