{"id":"007-jq-mcp-server","name":"jq-mcp-server","homepage":null,"repo_url":"https://github.com/007/jq-mcp-server","category":"automation","subcategories":[],"tags":["mcp","json","jq","data-transformation","go","command-execution","agent-tools"],"what_it_does":"Provides an MCP (Model Context Protocol) server that exposes `jq` as an MCP tool, executing jq expressions over provided JSON input. Communicates via JSON-RPC over stdin/stdout and is intended to run in a minimal container; jq is invoked via Go exec with context.","use_cases":["Use an LLM or MCP client to transform/query JSON using jq expressions","Data extraction from JSON payloads (e.g., logs, API responses)","On-the-fly JSON filtering without writing custom code","Building MCP-based automations that need deterministic JSON transformation"],"not_for":["Executing untrusted jq expressions without sandboxing concerns","Long-running/expensive jq operations without timeouts and limits","Using as an HTTP/web service for external clients (stdin/stdout MCP only)"],"best_when":"You have an MCP-compatible host/agent and you want a lightweight, deterministic JSON transform/query primitive via jq.","avoid_when":"You cannot control or constrain jq inputs/expressions (potential resource exhaustion) or you require network APIs/SDKs beyond MCP stdin/stdout.","alternatives":["Directly run jq in your own tooling/agent runtime","Write a small custom API that wraps jq with explicit quotas and authentication","Use another MCP tool provider for JSON transformation (if available)","Use an embedded JSON query language/library in your application (e.g., JMESPath)"],"af_score":56.0,"security_score":43.5,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:21:54.645449+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication described; the MCP server appears to be run locally (stdin/stdout) without auth mechanisms."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":56.0,"security_score":43.5,"reliability_score":22.5,"mcp_server_quality":78.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":0.0,"tls_enforcement":100.0,"auth_strength":0.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":80.0,"security_notes":"README claims execution safety via Go `exec.CommandContext`, non-root user (UID 1000), minimal scratch-based container, and no shell injection vulnerabilities. However, there is no mention of auth, sandboxing/quotas for jq execution, resource limits, or how errors are returned. Scratch/minimal image reduces attack surface but does not by itself prevent denial-of-service from expensive jq expressions.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"true","idempotency_notes":"Tool is a pure function of (expression, content) assuming jq execution has no side effects; repeated calls should yield the same result. (Exact idempotency depends on runtime constraints/timeouts not specified.)","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["jq expressions may fail on invalid JSON or syntax; server behavior and error payload format are not documented in the provided README","No documented resource/time limits: complex jq could cause high CPU/memory usage","No documented constraints/escaping rules beyond passing `content` as a string; agents should ensure proper JSON string encoding"]}}