Fetch JSONPath MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JSONRPC_MCP_PROXY | No | HTTP proxy configuration | |
| JSONRPC_MCP_VERIFY | No | SSL verification | true |
| JSONRPC_MCP_HEADERS | No | Custom headers (will be merged with default browser headers) | |
| JSONRPC_MCP_TIMEOUT | No | Request timeout in seconds | 10.0 |
| JSONRPC_MCP_FOLLOW_REDIRECTS | No | Follow redirects | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-jsonA | Extract JSON content from a URL using JSONPath with extended features. Supports extensions like len, keys, filtering, arithmetic operations, and more. If 'pattern' is omitted or empty, the entire JSON document is returned. Supports different HTTP methods (default: GET). |
| fetch-textC | Fetch text content from a URL using various HTTP methods. Defaults to converting HTML to Markdown format. |
| batch-fetch-jsonA | Batch extract JSON content from multiple URLs with different extended JSONPath patterns. Supports all JSONPath extensions and optimizes by fetching each unique request only once. Executes requests concurrently for better performance. Supports different HTTP methods. |
| batch-fetch-textA | Batch fetch raw text content from multiple URLs using various HTTP methods. Executes requests concurrently for better performance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: fetch-json and fetch-text handle single URL operations with JSONPath and raw text extraction respectively, while batch-fetch-json and batch-fetch-text handle multiple URLs with the same capabilities. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb-object pattern with hyphens (fetch-json, fetch-text, batch-fetch-json, batch-fetch-text). The naming convention is perfectly uniform across all four tools.
Four tools is an ideal number for this server's purpose of fetching and extracting content from URLs. It provides both single and batch operations for JSON and text, covering the domain efficiently without being too sparse or bloated.
The tool set covers the core fetching operations for JSON and text content with both single and batch capabilities, including support for various HTTP methods and JSONPath extensions. A minor gap is the lack of explicit tools for error handling or retry mechanisms, but agents can work around this.