Skip to main content
Glama
allxsmith

Bestax

by allxsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Bestax

No user-submitted related servers found.

    Related Servers

    • ui-react-mcp

      AlexCruzGargallo
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      MIT

    • Salt MCP

      feesch
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      6
      6 npm
      1
      MIT

    • free-design-registry

      erichon0410-png
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • Reacticx MCP

      igorfelipeduca
      A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      5
      11 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct lookup type (search, list, component detail, props, examples, CSS variables, helper props, class mapping, skills). The only mild overlap is get_component vs get_props, since get_component can also return a prop table, but the descriptions explicitly frame get_props as the cheaper subset so the choice is clear.

    Naming Consistency5/5

    Names are uniformly snake_case verb_noun patterns built from a small verb set (search_, list_, get_, lookup_). The convention is applied consistently across all ten tools, making the surface predictable.

    Tool Count5/5

    Ten tools is well within the ideal range and each earns its place by covering a distinct documentation facet. Nothing feels padded or missing in the tool roster itself.

    Completeness4/5

    For a component-library docs domain, the surface covers discovery (search/list), detail (component/props/examples/CSS), styling guidance (helper props, Bulma mapping), and task guides (skills). Coverage is strong; minor gaps like explicit version/compatibility lookup are not deal-breakers.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources