Skip to content
Vinkius

jmespath-query-executor Connector for AI agents.

3 live capabilities

Extract precise values from complex JSON datasets.

Live agent request jmespath-query-executor / Connector

Waiting for input…

AI Agent

Why people use jmespath-query-executor

Jmespath-query-executor solves the JSON inspection headache

With this MCP, you just tell your agent what you're looking for. It digs through the layers, finds the exact key, and hands it to you instantly.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get clean, filtered data without any manual parsing.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Parsing API Responses

    An engineer needs one specific ID from a 5MB JSON response and asks their agent to find it using `execute_jmespath_query`.

  2. Real-world use case 02

    Schema Verification

    A developer uses `inspect_json_schema` to confirm that a new microservice is sending the correct top-level keys.

  3. Real-world use case 03

    Automated Data Cleaning

    An automation specialist uses `validate_query_syntax` to ensure their batch processing queries are error-free before deployment.

Complete set · 3capabilities

The complete jmespath-query-executor capability set.

These are the exact actions your AI can choose when you ask it to work with jmespath-query-executor.

Capability set01 / 01

01—03

3 capabilities in this set.

Part of 3 available through jmespath-query-executor.

  1. 01 Capability

    Execute jmespath query

    Runs a specific query against your JSON data to pull out exactly what you need.

  2. 02 Capability

    Validate query syntax

    Checks your query string for errors before you try to run it against a dataset.

  3. 03 Capability

    Inspect json schema

    Looks at the top level of your JSON structure so you know which keys are available.

Set up in minutes

One URL. Then ask jmespath-query-executor to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use jmespath-query-executor from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_6aXPbraQWAHtprq4O0Qtanxssza6E78IBBMaRWJX/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it jmespath-query-executor, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable jmespath-query-executor for the conversation.

Where the request belongs

Work jmespath-query-executor can move forward.

Built around the request

Data engineers and backend developers who are tired of manually inspecting massive JSON responses to find a single nested key.

01

Data Engineer

Automating the extraction of specific metrics from API logs.

02

Backend Developer

Verifying that payload structures match expected schemas during testing.

03

DevOps Engineer

Parsing configuration files or deployment manifests to extract version numbers.

Bring your own AI

Change the model, client or framework. Keep jmespath-query-executor connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about jmespath-query-executor.

The practical details behind the request, access and result.

How can I use jmespath-query-executor to find data in large files?

You can ask your agent to run a query against the file, and it will return only the matching pieces of information.

Is jmespath-query-executor safe for production environments?

Yes, because it uses a deterministic syntax instead of executing arbitrary code or scripts.

Can I check my queries before running them with jmespath-query-executor?

You can use the validation capability to ensure your query string is structurally sound before you attempt to execute it.

Does jmespath-query-executor work with any JSON structure?

It works with any valid JSON, from simple key-value pairs to deeply nested arrays and objects.

How do I see the structure of a new dataset using jmespath-query-executor?

You can ask your agent to inspect the top-level keys so you know exactly what you're working with.

What tokens are supported in the query string?

The engine supports three primary tokens: '.' for property access, '[]' for array flattening, and '*' for wildcards.

How can I verify if my query is valid before running it?

You can use the validate_query_syntax capability to check your string for structural validity.

Does this capability modify my original JSON data?

No, the engine treats the input JSON as a read-only structure and builds a new resulting structure without modifying the source.

One connection away

Give your agent a direct line to jmespath-query-executor.

Connect jmespath-query-executor once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available