react-docs
Related Servers
Alternatives to react-docs
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for daisyUI React components that enables AI coding assistants to search documentation, look up props, and retrieve code examples.517 npm2MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides tools for React and TypeScript development, including generating typed form components, explaining TypeScript compiler errors, and producing Shadcn UI installation commands.312 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI assistants full access to PrimeReact v10 component documentation — props, events, examples, and search.51 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the ReactUse library. Exposes 110+ React Hook signatures, examples, and API metadata so AI coding assistants can discover and use any hook from @reactuses/core directly.31,054-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.11 npmISC
- AlicenseAqualityCmaintenanceMCP server for querying Preact documentation and ecosystem, including tools to search docs, get READMEs, and list packages.331 npm2MIT
TDQS
Scored across 5 tools
Tools are largely distinct: list_packages for enumeration, get_package_docs for README, get_package_source for arbitrary files, search_source for pattern search. However, get_package_types overlaps with get_package_source since both can retrieve types.ts, which may cause occasional confusion.
All tool names follow a consistent snake_case verb_noun pattern (list_, get_, search_), with clear and predictable wording.
Five tools is well-scoped for a documentation retrieval server, covering listing, fetching docs/types/source, and search without redundancy.
Core operations are present, but there is no tool to list files within a package, making get_package_source difficult to use without guessing file paths. This notable gap limits exploratory workflows.