JSON Query MCP

Created By
mgraczyka year ago
An MCP server that gives AI agents tools to query large JSON files
Overview

what is JSON Query MCP?

JSON Query MCP is a Model Context Protocol (MCP) server designed for querying large JSON files, providing tools for AI agents to efficiently work with extensive JSON data.

how to use JSON Query MCP?

To use JSON Query MCP, you can run the command npx json-query-mcp in your terminal. For integration, add the MCP server configuration to your cursor mcp json file.

key features of JSON Query MCP?

  • Query JSON files using JSONPath expressions.
  • Search for keys and values similar to a query string.
  • Efficiently handle large JSON data for AI applications.

use cases of JSON Query MCP?

  1. Extracting specific data from large JSON Swagger definitions.
  2. Assisting AI models in retrieving relevant information from extensive datasets.
  3. Facilitating data manipulation and analysis in JSON format.

FAQ from JSON Query MCP?

  • What is JSONPath?

JSONPath is a query language for JSON, similar to XPath for XML, allowing for easy data extraction from JSON structures.

  • Can I use JSON Query MCP with any JSON file?

Yes! JSON Query MCP can be used with any valid JSON file, making it versatile for various applications.

  • Is there a license for JSON Query MCP?

Yes, JSON Query MCP is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mgraczyk
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago