jq

This MCP server provides a dedicated tool named jq that lets you execute jq expressions against JSON content through the MCP protocol. The server runs in a container and exposes a JSON-RPC style interface over standard input/output, enabling clients to request an evaluation of a jq expression against supplied JSON data. To use it, send a request with the tool name (jq) and provide the parameters: expression (the jq filter) and content (the JSON string to operate on). The server will return the resulting JSON output produced by jq.

Available tool:

• jq: Execute a jq expression on JSON data. Parameters:
  • expression (required): The jq expression to apply (e.g., .name, .items[0].value, etc.).
  • content (required): A JSON string to process. For example: "{"name":"example", "value":42}". The server executes the expression against this content and returns the result.

Prerequisites:

• Docker installed on your machine (for container usage).
• Optional: Go tooling if you prefer to build from source and run locally.

Using the pre-built container image:

1. Pull and run the container: docker run -i ghcr.io/007/jq-mcp-server:latest

2. Interact via MCP client: send a JSON-RPC style request to the process’s stdin and read the response from stdout. The tool available is named jq, with parameters expression and content.

Building from source (optional):

1. Clone the repository: git clone https://github.com/007/jq-mcp-server.git
2. Build the container or binary as described in the repository (commonly a build script like build.sh): ./build.sh
3. Run locally (if built as a Go binary): go run main.go

Prerequisites for local development:

• Go toolchain (1.18+ typically).
• jq should not be required at runtime since this server embeds or downloads it during container build.

Tips and considerations:

• The server runs inside a minimal, scratch-based container for a small attack surface. It uses a non-root UID by default, aligning with good security practices.
• Content must be provided as a JSON string in the content parameter; ensure proper escaping when forming the request payload.
• This server is an independent MCP implementation and is not affiliated with the official jq project.
• Supports multi-architecture builds (amd64 and arm64) via the container image.
• If you need to customize behavior, refer to the repository’s build scripts and Dockerfile for how jq is wired into the Go binary and container image.