# JMeter Docs (remote · docs.jmeter.ai)

Apache JMeter community documentation, conversion tools, linters, and calculators for AI agents.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `docs.jmeter.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp.md), [page](https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp)

## Channel facts

- Endpoint: `https://docs.jmeter.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 49/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1653 tokens (~165/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the JMeter Docs MCP server?

JMeter Docs is a hosted endpoint at https://docs.jmeter.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http qainsights-jmeter-docs 'https://docs.jmeter.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "qainsights-jmeter-docs": {
      "url": "https://docs.jmeter.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "qainsights-jmeter-docs": {
      "type": "http",
      "url": "https://docs.jmeter.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.qainsights-jmeter-docs]
url = "https://docs.jmeter.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qainsights-jmeter-docs": {
      "type": "remote",
      "url": "https://docs.jmeter.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qainsights-jmeter-docs --url 'https://docs.jmeter.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  qainsights-jmeter-docs:
    url: "https://docs.jmeter.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "qainsights-jmeter-docs": {
      "Transport": "http",
      "Url": "https://docs.jmeter.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add qainsights-jmeter-docs -t streamable-http -u 'https://docs.jmeter.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "qainsights-jmeter-docs": {
      "type": "http",
      "url": "https://docs.jmeter.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 60)

First indexed and scored.

## MCP tools (10)

### `search_jmeter_docs` (~85 tokens)

Search JMeter documentation

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.

Input parameters:

- `query` (string, required): Search query, e.g. "how to correlate dynamic values" or "thread group ramp up"

### `get_jmeter_page` (~87 tokens)

Read a JMeter documentation page

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).

Input parameters:

- `url` (string, required): Page URL or path, e.g. https://docs.jmeter.ai/user-manual/functions/ or user-manual/functions

### `lint_jmx_snippet` (~79 tokens)

Lint JMX Test Plan Snippet

Validate a JMeter test plan XML string or snippet against best practices and performance anti-patterns (e.g., active GUI listeners, legacy BeanShell, uncompiled JSR223, missing timeouts, zero ramp-up, Thread.sleep in scripts).

Input parameters:

- `jmxContent` (string, required): JMX XML string or test plan snippet to analyze.

### `calculate_workload_model` (~149 tokens)

Calculate Workload Model & Little's Law Sizing

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.

Input parameters:

- `avgResponseTimeMs` (number, required): Expected average response time in milliseconds.
- `safetyFactor` (number): Headroom safety buffer multiplier (default: 1.25 = 25% buffer).
- `targetRps` (number, required): Target throughput in requests / transactions per second (RPS/TPS).
- `testDurationMinutes` (number): Steady-state test duration in minutes (default: 10).
- `thinkTimeMs` (number): Think time / user pause between requests in milliseconds (default: 0).

### `lookup_jmeter_property` (~87 tokens)

Lookup JMeter Tuning Property

Search or lookup curated JMeter properties (e.g. "httpclient4.idletimeout", "jmeter.save.saveservice.*", "remote_hosts", "summariser"). Returns category, defaults, and recommendations.

Input parameters:

- `query` (string, required): Property name or keyword to search (e.g. "ssl", "timeout", "jtl", "influxdb").

### `get_jsr223_recipe` (~105 tokens)

Get Verified JSR223 Groovy Recipe

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).

Input parameters:

- `query` (string): Filter by keyword or topic (e.g. "jwt", "hmac", "header", "json", "csv", "logging"). If omitted, returns all recipes.

### `lookup_error_playbook` (~98 tokens)

Lookup Error & Exception Diagnostic Playbook

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").

Input parameters:

- `query` (string, required): Error message, exception name, or status (e.g. "bindexception", "heap", "timeout", "401").

### `plan_distributed_testing` (~237 tokens)

Plan Distributed Testing Ports & Firewall Rules

Generate Master-Worker RMI port assignments, user.properties, CLI commands, firewall/security group rules, and Docker Compose manifests for distributed load testing.

Input parameters:

- `clientRmiLocalPort` (integer): Pinned controller callback port (default: 60000).
- `controllerIp` (string): Controller / Master node IP or hostname (default: "10.0.0.5").
- `disableSsl` (boolean): Disable RMI SSL (default: false). Only for isolated labs.
- `environment` (string): Target infrastructure environment for firewall/CLI rules (default: "aws").
- `mode` (string): Sample transmission mode (default: "StrippedBatch").
- `serverPort` (integer): RMI registry port on workers (default: 1099).
- `serverRmiLocalPort` (integer): Pinned worker engine port (default: 50000).
- `workerIps` (string, required): Comma or space-separated list of worker / injector IP addresses (e.g. "10.0.1.10, 10.0.1.11, 10.0.1.12").

### `tune_linux_os` (~169 tokens)

Linux Kernel & OS Tuning for Load Injectors

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).

Input parameters:

- `concurrency` (integer): Target concurrent connections/threads (default: 10000).
- `ramGb` (integer): Host machine RAM in GB for TCP buffer sizing (default: 16).
- `role` (string): Machine role: "injector" (JMeter client) or "target_sut" (default: "injector").
- `targetDistro` (string): Linux distro or container target (default: "ubuntu_debian").
- `trafficType` (string): Traffic profile (default: "http_churn").

### `convert_curl_or_har_to_jmx` (~326 tokens)

Convert cURL or HAR to JMeter JMX Test Plan

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.

Input parameters:

- `durationSeconds` (integer): Test duration in seconds (0 = disabled, default: 0).
- `filterStaticAssets` (boolean): Filter out images/css/fonts when parsing HAR (default: true).
- `includeAssertions` (boolean): Add HTTP 200/201/204 Response Code assertions (default: true).
- `includeCookieManager` (boolean): Include HTTP Cookie Manager (default: true).
- `input` (string, required): cURL command string (single, multiline, or batch) or HAR 1.2 JSON text (max 1MB).
- `loopCount` (integer): Loop count (-1 for infinite, default: 1).
- `parameterizeAuth` (boolean): Extract Bearer token into ${AUTH_TOKEN} variable (default: true).
- `parameterizeHost` (boolean): Extract common host into HTTP Request Defaults and ${BASE_URL} (default: true).
- `rampUpSeconds` (integer): Ramp-up time in seconds (default: 1).
- `testPlanName` (string): Name of the JMeter Test Plan (default: "cURL Converted Plan").
- `threads` (integer): Thread concurrency / virtual users (default: 1).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp#diagnostics

## Score history

- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 64
- 2026-09-15: 64
- 2026-09-14: 63
- 2026-09-13: 63
- 2026-09-12: 62
- 2026-09-11: 62
- 2026-09-10: 61
- 2026-09-09: 61
- 2026-09-08: 60

## Common questions

### What is the JMeter Docs MCP server?

JMeter Docs is an MCP server listed in the public MCP registry as io.github.QAInsights/jmeter-docs. Apache JMeter community documentation, conversion tools, linters, and calculators for AI agents. This page covers its hosted endpoint (https://docs.jmeter.ai/api/mcp).

### Is the JMeter Docs MCP server safe to use?

JMeter Docs scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the JMeter Docs MCP server expose?

JMeter Docs exposes 10 tools: search_jmeter_docs, get_jmeter_page, lint_jmx_snippet, calculate_workload_model, lookup_jmeter_property, and 5 more. Their descriptions and schemas cost roughly 1,422 tokens of context every time the server is loaded.

### Does the JMeter Docs MCP server require authentication?

No. We connected to JMeter Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the JMeter Docs MCP server still maintained?

JMeter Docs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://docs.jmeter.ai/api/mcp
- Repository: https://github.com/QAInsights/docs.jmeter.ai
- Website: https://docs.jmeter.ai/
- Changelog RSS feed: https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qainsights-jmeter-docs/api-mcp