Bestax
Related Servers
Alternatives to Bestax
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to query accurate, up-to-date documentation for a React component library, including component lists, search, props, allowed values, defaults, and validated JSX usage examples over stdio.4MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to private React component library documentation, props, and code examples through type-safe TypeScript integration.-
- AlicenseAqualityDmaintenanceEnables AI agents to build React applications using JP Morgan Chase's Salt Design System by providing real-time access to component APIs, documentation, and accessibility guidelines. It supports tasks such as scaffolding new projects, building UI patterns, and converting Figma designs into Salt code via the Model Context Protocol.69 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search a fully local catalog of 21st-style shadcn components via full-text search, inspect individual records, generate reusable build prompts, retrieve install steps, and fetch design tokens for aesthetic keywords. Runs entirely offline over stdio with no API keys, paywalls, or rate limits.Apache 2.0
- AlicenseAqualityDmaintenanceProvides documentation and component references for the Reacticx React Native library, including props, code examples, and installation guides. It enables users to search through over 90 components and retrieve setup commands for project dependencies.53 npm2MIT
TDQS
Scored across 10 tools
Each tool targets a distinct information type (props, examples, CSS variables, skills, class lookup), but get_component is effectively a superset that can emit props/examples/CSS variables via its `include` parameter, overlapping get_props, get_examples and get_css_variables. The descriptions resolve this by framing the specialized tools as cheaper, narrower alternatives, so boundaries are mostly clear but not perfectly orthogonal.
Names follow a predictable verb_noun pattern throughout: get_component, get_props, get_examples, get_css_variables, get_helper_props, list_components, list_skills, get_skill, lookup_bulma_classes, search_bestax. Minor deviation is the singular/plural mismatch between list_components/get_component and list_skills/get_skill, but conventions are otherwise consistent and readable.
Ten tools is well-scoped for a component-library documentation server. Discovery (search_bestax, list_components), retrieval (get_component, get_props, get_examples, get_css_variables), helper guidance (get_helper_props, lookup_bulma_classes) and skills (list_skills, get_skill) each earn their place with no redundancy.
The surface covers the full documentation lifecycle: search, list, detailed retrieval, prop tables, runnable examples, CSS variable theming, helper props, Bulma class mapping, and task-level skills. Coverage is strong for a docs server, with only minor gaps such as no explicit version/migration or changelog retrieval beyond what a skill might supply.