Point Claude Code, Qwen Code, Cursor, or any MCP client at https://docs.jmeter.ai/api/mcp and your agent answers JMeter questions grounded in this documentation, with a source link for every answer. Free, no API key, no signup.
Scored across 16 tools
Most tools target distinct actions: conversion (curl/HAR vs OpenAPI), linting (Groovy vs JMX), and generation (sandbox, distributed, OS tuning) are clearly separated. The reference-lookup cluster (search_jmeter_docs, lookup_component, lookup_function, lookup_jmeter_property, get_jmeter_page) and the error cluster (triage_errors vs lookup_error_playbook) have mild conceptual overlap, but descriptions distinguish their scopes (search vs specific-entity reference; symptom triage vs exception lookup).
Names follow a consistent snake_case verb_noun pattern throughout (get_*, lookup_*, convert_*, lint_*, plan_*). Minor verb variety (get vs lookup) is still predictable and readable, with no camelCase mixing or chaotic conventions.
16 tools sits at the upper edge but is justified by a genuinely broad domain (test-plan authoring, doc lookup, linting, distributed setup, OS tuning, error triage). Each tool maps to a distinct workflow rather than being redundant.
Strong coverage of the authoring/configuration lifecycle: conversions, workload modeling, distributed planning, OS tuning, linting, and troubleshooting. Minor gaps remain around actually executing tests or generating/analyzing HTML dashboard reports, which an agent would have to work around externally.
Compute required thread concurrency, pacing delays, ramp-up schedules, and JVM heap recommendations based on target RPS/TPS and SLA response times using Little's Law.
Inputs: targetRps (required), avgResponseTimeMs (required), thinkTimeMs, safetyFactor, +1 more.
Convert one or more cURL commands or HAR (HTTP Archive 1.2) JSON traces into a valid, production-ready Apache JMeter .jmx test plan XML with HTTP Request Defaults, Header Managers, Cookie Managers, timeouts, and assertions. Supports GET, POST, PUT, DELETE, PATCH, and RFC 9838 QUERY methods.
Inputs: input (required), threads, loopCount, testPlanName, +7 more.
Convert an OpenAPI 3.0/3.1 or Swagger 2.0 document (JSON or YAML) into a JMeter 5.6.3 .jmx test plan: servers become HTTP Request Defaults/${BASE_URL}, path parameters become User Defined Variables, request bodies are sampled from schemas, bearer/basic/apiKey security becomes ${AUTH_TOKEN}/${BASIC_AUTH}/${API_KEY}, with optional method, tag, and deprecated-operation filters.
Inputs: input (required), tags, methods, threads, +12 more.
Generate a ready-to-run Apache JMeter 5.6.3 .jmx practice test plan (either "solved" with Boundary/JSON/Header extractors or "challenge" with broken hardcoded tokens) targeting the live docs.jmeter.ai/api/sandbox endpoints or local localhost:8787 server.
Inputs: mode, flowId, target.
Fetch the full markdown text of one docs.jmeter.ai page. Accepts the page URL (e.g. https://docs.jmeter.ai/topics/api-load-testing/) or a bare path (e.g. topics/api-load-testing).
Inputs: url (required).
Fetch production-ready, performant Groovy scripts for JMeter JSR223 samplers, preprocessors, and postprocessors (e.g., JWT parsing & expiration, HMAC-SHA256 signing, dynamic header injection, nested JSON array extraction, custom CSV failure logging).
Inputs: query.
Statically analyze a Groovy script for a JMeter JSR223 element. Flags Thread.sleep, ${var} interpolation, System.out, BeanShell APIs, per-call Random or Pattern.compile, and bindings such as prev, SampleResult, or sampler that the selected element type does not expose; optionally returns ready-to-paste JMX element XML.
Inputs: code (required), name, parameters, elementType, +1 more.
Validate a JMeter test plan XML string or snippet against best practices and performance anti-patterns, and return a structural inventory with thread groups, sampler/listener/assertion counts, HTTP Defaults/Header/Cookie/CSV presence, plugin classes, and JMeter version.
Inputs: jmxContent (required).
Find the dedicated reference page for a JMeter test plan component (e.g. "HTTP Request", "JSON Extractor", "Thread Group") and return its full markdown content with properties, defaults, and related guides.
Inputs: name (required).
Get immediate root causes, OS/JVM config fixes, and remediation steps for common JMeter exceptions (e.g. "BindException", "SocketTimeoutException", "OutOfMemoryError", "NoHttpResponseException", "SSLHandshakeException", "401/403 after recording"). When keywords miss, unmatched text is sent to classifier.dev for zero-shot semantic matching (public keyless calls are not stored).
Inputs: query (required), classifierApiKey.
Find the dedicated reference page for a built-in JMeter function (e.g. "__time", "__Random", "__P") and return its full markdown content with syntax, parameters, and examples.
Inputs: name (required).
Search or lookup curated JMeter properties (e.g. "httpclient4.idletimeout", "jmeter.save.saveservice.*", "remote_hosts", "summariser"). Returns category, defaults, and recommendations.
Inputs: query (required).
Generate Master-Worker RMI port assignments, user.properties, CLI commands, firewall/security group rules, and Docker Compose manifests for distributed load testing.
Inputs: workerIps (required), mode, disableSsl, serverPort, +4 more.
Search the Apache JMeter documentation on docs.jmeter.ai. Returns the most relevant pages with titles, URLs, and snippets. Use for any question about JMeter test plans, components, functions, properties, distributed testing, reports, or troubleshooting.
Inputs: query (required).
Map a run's distinct failure signatures to docs.jmeter.ai error playbooks. Error text is sent to classifier.dev for zero-shot classification (public keyless calls are not stored; obvious secrets are redacted first). Prefer signatures shaped as "sampler | response code | response message".
Inputs: errors (required), tier, minConfidence, classifierApiKey.
Generate production sysctl.conf, limits.conf, systemd overrides, and Docker/K8s configs tuned for high-concurrency JMeter load testing (fixing ulimit nofile, BindException port exhaustion, somaxconn backlog, and JVM swappiness).
Inputs: role, ramGb, concurrency, trafficType, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
