react-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token to avoid rate limits. Generate at GitHub Settings > Developer Settings > Personal access tokens. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_packagesA | List all available @gaddario98 React packages with their descriptions and GitHub links |
| get_package_docsB | Get the full README.md documentation for a specific @gaddario98 React package |
| get_package_typesB | Get the TypeScript type definitions (types.ts) for a specific @gaddario98 React package |
| get_package_sourceA | Read the contents of a specific source file from a @gaddario98 React package. Use list_packages first to see available packages, then explore files. |
| search_sourceA | Search for a pattern across all source files of a @gaddario98 React package using GitHub Code Search. Requires GITHUB_TOKEN environment variable for best results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| react-core-readme | @gaddario98/react-core — full README documentation |
| react-form-readme | @gaddario98/react-form — full README documentation |
| react-queries-readme | @gaddario98/react-queries — full README documentation |
| react-pages-readme | @gaddario98/react-pages — full README documentation |
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.