Fetch Jsonpath Mcp

Created By
ackness10 months ago
A Model Context Protocol (MCP) server that provides tools for fetching and extracting JSON data from URLs using JSONPath patterns.
Overview

What is Fetch Jsonpath MCP?

Fetch Jsonpath MCP is a Model Context Protocol (MCP) server designed to fetch and extract JSON data from URLs using JSONPath patterns, enabling efficient data retrieval and web scraping.

How to use Fetch Jsonpath MCP?

To use Fetch Jsonpath MCP, install it using the uvx tool and run the server. You can then make requests to extract specific data from JSON responses using defined JSONPath patterns.

Key features of Fetch Jsonpath MCP?

  • Intelligent content extraction using JSONPath patterns.
  • Support for multiple HTTP methods (GET, POST, etc.).
  • Browser-like headers for reliable web scraping.
  • Batch processing of multiple URLs with different JSONPath patterns.

Use cases of Fetch Jsonpath MCP?

  1. Extracting specific fields from large JSON responses to save on token usage.
  2. Fetching web content with intelligent text extraction for better readability.
  3. Processing multiple API requests concurrently to gather data efficiently.

FAQ from Fetch Jsonpath MCP?

  • Can Fetch Jsonpath MCP handle all types of JSON data?

Yes! It is designed to work with any JSON data that can be accessed via a URL.

  • Is Fetch Jsonpath MCP free to use?

Yes! It is open-source and available for anyone to use.

  • How does Fetch Jsonpath MCP improve efficiency?

By allowing users to extract only the necessary data, it reduces token usage and speeds up processing.

Server Config

{
  "mcpServers": {
    "fetch-jsonpath-mcp": {
      "command": "uvx",
      "args": [
        "fetch-jsonpath-mcp"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
9 months ago
Author Name
ackness
Star
-
Language
-
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