JSX Prop Lookup MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_ROOTS | No | Comma-separated list of allowed root directories (absolute or workspace-relative) to restrict filesystem access. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_jsx_propsA | Analyze JSX/React component prop usage across files and directories. Use this tool when you need to:
EXAMPLES:
Returns:
|
| find_prop_usageA | Find all usages of a specific prop across JSX/React files. Use this tool when you need to:
EXAMPLES:
Returns:
|
| get_component_propsA | Get detailed information about all props used by a specific component. Use this tool when you need to:
EXAMPLES:
Returns:
|
| find_components_without_propA | Find component instances that are missing a required prop (e.g., Select components without width prop). Use this tool when you need to:
EXAMPLES:
Returns:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Tools have distinct purposes, but 'analyze_jsx_props' with a component name overlaps with 'get_component_props'. Descriptions help differentiate, but an agent might be unsure which to use for listing props of a single component.
All tool names follow a consistent verb_noun snake_case pattern (e.g., 'analyze_jsx_props', 'find_components_without_prop'), making them predictable and easy to parse.
With 4 tools, the server is well-scoped for JSX prop lookup. Each tool has a clear role, and the count is neither too sparse nor excessive for the domain.
The tool surface covers major lookup needs (analyze props, find missing props, find prop usage, get component props). A minor gap is the lack of a tool to list all components without analyzing props, but the set is functional for its purpose.