Jmespath Mcp
Transform and query JSON data structures using JMESPath expressions in your backend, API, or agent workflows without external dependencies.
Overview
io.github.MukundaKatta/jmespath-mcp is a Build-phase MCP server that runs JMESPath queries against JSON so agents can extract and reshape structured data without custom scripts.
What is this MCP server?
- Pure JavaScript implementation—no native binaries or external services required
- Fast JMESPath query execution for JSON transformation and filtering
- Perfect for AI agents, APIs, and backend services that process structured data
What problem does it solve?
API and webhook JSON is too nested to paste whole into prompts, and writing ad-hoc jq or Python filters breaks flow every time the agent needs a new projection.
Who is it for?
Solo builders wiring agent workflows who already have JSON in hand and need fast, repeatable field selection.
Skip if: Teams that need full ETL pipelines, SQL over tables, or HTTP fetching—use dedicated data or browser MCP servers first.
What do I get? / Deliverables
Your agent can apply JMESPath expressions in-tool and return precise JSON subsets ready for typing, tests, or downstream MCP steps.
- JMESPath-filtered JSON fragments for prompts or code generation
- Repeatable query expressions you can reuse across fixtures
- Registered stdio MCP server in your local agent config
Recommended MCP Servers
Journey fit
This tool belongs in the build phase because it directly solves the core problem of JSON transformation during active development and integration work. Backend integration is the right subphase since JMESPath querying is fundamental to processing JSON in server-side logic, APIs, and data pipelines.
How it compares
JMESPath query MCP utility, not a REST client skill or a document database connector.
Common Questions / FAQ
Who is jmespath-mcp for?
Indie and solo developers using Claude Code or Cursor who want agents to query JSON structures with JMESPath during integration and backend work.
When should I use jmespath-mcp?
Use it when you have JSON fixtures, API responses, or config dumps and need filtered slices for prompts, codegen, or validation without leaving MCP.
How do I add jmespath-mcp to my agent?
Install @mukundakatta/jmespath-mcp from npm, add a stdio MCP server entry pointing at the package binary, restart the host, and invoke the JMESPath tools from chat.