JSX Prop Lookup MCP Server
This MCP server analyzes JSX/React component props across a codebase without executing or editing source files.
Analyze components and their props in files or directories, optionally including TypeScript type information.
Find all usages of a specific prop, with file paths, line numbers, and passed values.
Inspect all props used by a named component, including types, defaults, and usage statistics.
Find component instances missing a required prop, with locations, existing props, and summary counts.
Filter analysis by component name, prop name, path/directory, and type-inclusion options.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JSX Prop Lookup MCP Server find usages of prop 'disabled' in Select components"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JSX Prop Lookup MCP Server
Find JSX call sites, inspect component props, and run saved prop rules from the command line or an MCP client. Analysis reads JavaScript and TypeScript without executing application code or editing source files.
Install and run
Node.js 24.11.0 or newer is required.
npm install --global jsx-prop-lookup-mcp-server
jsx-prop-lookup-mcp-server query --project-root /workspace/app --component Button --json
jsx-prop-lookup-mcp-server inspect --project-root /workspace/app --component Button
jsx-prop-lookup-mcp-server check --project-root /workspace/app --rules checks/props.json --jsonYou can also prefix commands with npx --yes jsx-prop-lookup-mcp-server.
Running the executable without a command starts the MCP stdio server;
serve selects that behavior explicitly. See the CLI reference
for flags, output, and exit codes, and saved checks
for the versioned JSON rules schema.
Related MCP server: tsx-query
MCP client configuration
The default MCP server exposes three read-only tools: find_jsx,
inspect_component, and check_jsx.
{
"mcpServers": {
"jsx-prop-lookup": {
"command": "npx",
"args": ["--yes", "jsx-prop-lookup-mcp-server"],
"env": {
"PROJECT_ROOT": "/workspace/app",
"ALLOWED_ROOTS": "/workspace/app"
}
}
}
}For a local build, use node as the command and the absolute path to
dist/index.js as its first argument. See the CLI reference for
project-root and filesystem options.
Tools
Tool | Purpose | Reference |
| Find JSX call sites by component and prop. | |
| Inspect declared props, types, and static defaults. | |
| Check required, deprecated, and forbidden props. |
For saved rule files, see the schema and examples. For filesystem restrictions, see SECURITY.md.
Compatibility
Existing beta clients can select --legacy-tools for the original tool set; see
the CLI reference for compatibility details.
Legacy prop-key, forwarding, and baseline analysis is documented in the legacy analysis reference.
Parser/API research and reproducible local measurements are in the AST modernization report.
Development
Release maintainers: see automatic npm publishing for the
one-time OIDC trusted-publisher setup and release behavior after merging to master.
git clone https://github.com/lmn451/jsx-prop-lookup-mcp-server.git
cd jsx-prop-lookup-mcp-server
npm install
npm run build
npm test
npm startnpm run dev -- query --component Button --json runs source directly.
src/cli.ts shares parsing and command execution; src/index.ts owns process I/O
and lifecycle. src/server.ts registers the modern tools, while
src/legacy-server.ts keeps the compatibility registrations separate.
Run the checked-in migration and audit examples to try caller search, component inspection, and saved checks with stated results.
Preview a proposed prop removal with inspect --component Button --remove-prop variant.
See change impact and the runnable migration examples.
Available Tools
4 toolsanalyze_jsx_propsA
Analyze JSX/React component prop usage across files and directories.
Use this tool when you need to:
Understand what props a component accepts
Find all components in a codebase and their props
Analyze prop usage patterns in a project
Get TypeScript interface information for components
EXAMPLES:
Analyze all components in current directory: { "includeTypes": true }
Analyze all components in src/components: { "path": "src/components", "includeTypes": true }
Find all props for Button component in current directory: { "componentName": "Button", "includeTypes": true }
Find all usages of onClick prop in current directory: { "propName": "onClick", "includeTypes": false }
Analyze specific file with type info: { "path": "src/App.tsx", "includeTypes": true }
Returns:
Component names and their props
Prop types (when includeTypes is true)
File locations where components are defined
Inputs: path, componentName, propName, includeTypes.
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:
Audit components for missing required props
Ensure accessibility props are present (e.g., missing aria-label)
Check for missing styling props (e.g., missing width or height)
Enforce prop requirements across the codebase
Refactor components and ensure all usages are updated
EXAMPLES:
Find Select components missing width prop in current directory: { "componentName": "Select", "requiredProp": "width" }
Audit Image components for missing alt text in current directory: { "componentName": "Image", "requiredProp": "alt" }
Find Button components missing type prop in src directory: { "componentName": "Button", "requiredProp": "type", "directory": "src" }
Check Input components for missing label in forms directory: { "componentName": "Input", "requiredProp": "aria-label", "directory": "src/forms" }
Returns:
List of component instances missing the required prop
File paths and line numbers
Existing props on those instances
Summary statistics (total instances vs missing count)
Inputs: componentName (required), requiredProp (required), directory.
find_prop_usageA
Find all usages of a specific prop across JSX/React files.
Use this tool when you need to:
Locate where a prop is used throughout the codebase
Find all components that use a specific prop like "onClick", "className", etc.
Audit prop usage for refactoring or deprecation
Understand prop propagation patterns
EXAMPLES:
Find all onClick handlers in current directory: { "propName": "onClick" }
Find className usage in components directory: { "propName": "className", "directory": "src/components" }
Find variant prop only on Button components in current directory: { "propName": "variant", "componentName": "Button" }
Find all disabled props in specific directory: { "propName": "disabled", "directory": "src/forms" }
Returns:
List of component instances using the prop
File paths and line numbers
Values passed to the prop
Inputs: propName (required), directory, componentName.
get_component_propsA
Get detailed information about all props used by a specific component.
Use this tool when you need to:
Understand what props a component accepts and uses
Document component APIs
Check if a component has certain props before using it
Analyze component interfaces
EXAMPLES:
Get all props for Button component in current directory: { "componentName": "Button" }
Check Modal component props in specific directory: { "componentName": "Modal", "directory": "src/components" }
Document Card component API in UI directory: { "componentName": "Card", "directory": "src/ui" }
Analyze Input component interface in current directory: { "componentName": "Input" }
Returns:
All props used by the component
Prop types and default values
Usage statistics across the codebase
Inputs: componentName (required), directory.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
Related MCP Servers
- FlicenseNot gradedqualityDmaintenance* analyze your react projects locally * consistent output w/ AST parsing + AI * create markdown docs, llm.txt for your react code at once58-
- AlicenseAqualityDmaintenanceSemantic React/TSX analysis MCP server that saves 70-90% tokens by using AST to retrieve precise component usages, prop flow, and state update information for AI coding assistants.1010 npmMIT
- AlicenseNot gradedqualityFmaintenanceAnalyzes JSX component prop usage in React/JSX codebases, enabling detection of specific props, missing props, and substring matching for prop values.ISC
- AlicenseNot gradedqualityDmaintenanceEnables searching for component, function, and type usage in React/TypeScript projects.13 npmMIT