feat(registry): add Bestax MCP server

[allxsmith]

Adds mcp-registry/servers/bestax-mcp.json for bestax-mcp, the MCP server for Bestax (React components for Bulma v1). I maintain it.

• npm: https://www.npmjs.com/package/bestax-mcp (MIT)
• Source: https://github.com/allxsmith/bestax/tree/main/bestax-mcp
• Docs: https://bestax.io/docs/guides/llms#mcp-server
• Official MCP Registry name: io.github.allxsmith/bestax-mcp

It runs locally over stdio with npx -y bestax-mcp@1, works offline and needs no API key. The tool list matches the server's README. I checked the file against server-schema.json by hand.

Summary by CodeRabbit

• New Features
  • Added Bestax MCP to the registry, with project details, descriptions of its tools, installation instructions, and example prompts.
  • Listed it as an official server and noted its offline operation without an API key.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 71242c0f-a280-469e-9d6d-adfe12904bd4

📥 Commits

Reviewing files that changed from the base of the PR and between 936cd00 and 70a61e2.

📒 Files selected for processing (1)

• mcp-registry/servers/bestax-mcp.json

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The registry now includes a Bestax MCP entry with project metadata, ten tool descriptions, npm installation details, example prompts, and an official designation.

Changes

Bestax MCP registry entry

Layer / File(s)	Summary
Add Bestax server metadata mcp-registry/servers/bestax-mcp.json	Adds project metadata, ten tool descriptions, an npx bestax-mcp@1 installation requiring Node.js 22 or later, three example prompts, and an official designation.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 70a61

The listing conforms to the checked-in registry shape, and Bestax documentation describes bestax-mcp as first-party. No concrete mismatch is established, so the change appears ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly states the main change: adding the Bestax MCP server to the registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again manually by commenting /agentic_review on this PR.

[qodo-code-review]

PR Summary by Qodo

Add Bestax MCP server to the registry

✨ Enhancement 🕐 Less than 10 minutes

AI Description

• Register Bestax MCP so clients can discover its Bulma v1 React development tools.
• Document its local npm installation, capabilities, and example prompts for getting started.

Diagram

graph TD
  Registry["Registry manifest"] --> Client["MCP client"] --> Server["Bestax MCP server"] --> Index["Bundled Bestax index"]

Loading

High-Level Assessment

A standalone registry manifest is the appropriate approach for an existing npm-distributed server. The local stdio installation preserves its offline, no-API-key use case; a hosted endpoint would add an unnecessary dependency.

Files changed (1) +99 / -0

Enhancement (1) +99 / -0

bestax-mcp.jsonRegister the Bestax MCP server +99/-0

Register the Bestax MCP server

• Adds Bestax's repository, author, license, category, and discovery tags. Lists ten tools, a recommended Node.js 22+ npm/stdio launch command, and three example prompts for component development, Bulma conversion, and theming.

mcp-registry/servers/bestax-mcp.json

[Copilot]

Copilot review overview

🟢 Approval recommended

The manifest matches the registry schema and upstream package documentation.

Review effort: Balanced
Findings: None

What changed in this PR

Adds Bestax’s official MCP server to the registry.

Changes:

• Defines Bestax metadata, tools, installation, and usage examples.
• Configures local stdio execution through npx.

File	Description
mcp-registry/​servers/​bestax-mcp.json	Adds the schema-compliant Bestax server manifest.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.