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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago