loading…
Search for a command to run...
loading…
Analyzes JSX prop usage in React/TypeScript codebases using AST parsing, enabling prop usage tracking, component analysis, and TypeScript support.
Analyzes JSX prop usage in React/TypeScript codebases using AST parsing, enabling prop usage tracking, component analysis, and TypeScript support.
An MCP (Model Context Protocol) server that analyzes JSX prop usage in React/TypeScript codebases using AST parsing.
p.onClick and buttonProps.disabled inside function/arrow component bodiesNo installation required! Use directly with npx:
npx jsx-prop-lookup-mcp-server
npm install -g jsx-prop-lookup-mcp-server
jsx-prop-lookup-mcp-server
git clone https://github.com/your-username/jsx-prop-lookup-mcp-server.git
cd jsx-prop-lookup-mcp-server
npm install
npm run build
npm start
The server provides four main tools:
analyze_jsx_propsAnalyze JSX prop usage in files or directories.
Parameters:
path (required): File or directory path to analyzecomponentName (optional): Specific component name to analyzepropName (optional): Specific prop name to search forincludeTypes (optional): Include TypeScript type information (default: true)find_prop_usageFind all usages of a specific prop across JSX files. The directory must be an absolute path.
Parameters:
propName (required): Name of the prop to search fordirectory (optional): Directory to search in (default: "."). Must be an absolute path.componentName (optional): Limit search to specific componentget_component_propsGet all props used by a specific component. The directory must be an absolute path.
Parameters:
componentName (required): Name of the component to analyzedirectory (optional): Directory to search in (default: "."). Must be an absolute path.find_components_without_propFind component instances that are missing a required prop (e.g., Select components without width prop). The directory must be an absolute path.
Parameters:
componentName (required): Name of the component to check (e.g., "Select")requiredProp (required): Name of the required prop (e.g., "width")directory (optional): Directory to search in (default: "."). Must be an absolute path.{
"summary": {
"totalFiles": 5,
"totalComponents": 3,
"totalProps": 12
},
"components": [
{
"componentName": "Button",
"file": "./src/Button.tsx",
"props": [
{
"propName": "onClick",
"componentName": "Button",
"file": "./src/Button.tsx",
"line": 5,
"column": 10
}
],
"propsInterface": "ButtonProps"
}
],
"propUsages": [
{
"propName": "className",
"componentName": "Button",
"file": "./src/App.tsx",
"line": 15,
"column": 20,
"value": "btn-primary"
}
]
}
UI.Select) are supported. You can target either the full dotted name (e.g., UI.Select) or the local component name (e.g., Select) in tool inputs. Results record the full dotted name where applicable..js - JavaScript.jsx - JavaScript with JSX.ts - TypeScript.tsx - TypeScript with JSXAdd to your MCP client configuration:
{
"mcpServers": {
"jsx-prop-lookup": {
"command": "npx",
"args": ["jsx-prop-lookup-mcp-server"]
}
}
}
{
"mcpServers": {
"jsx-prop-lookup": {
"command": "jsx-prop-lookup-mcp-server"
}
}
}
{
"mcpServers": {
"jsx-prop-lookup": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "/path/to/jsx-prop-lookup-mcp-server"
}
}
}
npm run dev # Run in development mode
npm run build # Build for production
npm start # Run built version
Run in your terminal:
claude mcp add jsx-prop-lookup-mcp-server -- npx Security
Low riskAutomated heuristic from public metadata — not a security guarantee.