jq-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_PATHS | No | Comma-separated list of directories allowed for file access. Overrides default (cwd, /tmp). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jqA | Runs a jq query against a JSON file, gated by an allowlist of directories. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, singular purpose.
The sole tool is named 'jq', which is concise and directly reflects its function. While it does not follow a verb_noun pattern, there is no inconsistency since there is only one tool.
A single tool for running jq queries is slightly below the typical 3-15 range, but it is reasonable for a focused utility that performs one specific operation.
The server provides the core jq query functionality, but lacks supporting tools such as listing available files or directories, which may cause agent failures when needing to discover inputs.