Security & Testing

jmeter.ai

Provides tools for searching JMeter documentation, validating test plan XML, calculating workload models, and looking up JMeter properties to assist with performance testing.

1 endpoint10 known toolsFirst detected September 9, 2026Last detected September 9, 2026

ENDPOINT 1

https://docs.jmeter.ai/api/mcp

No auth detected

MCP server metadata

Name: jmeter-docs
Version: 1.4.0

Capabilities

tools.listChanged

Server instructions

You have access to the Apache JMeter community documentation at https://docs.jmeter.ai and built-in JMeter diagnostic/calculation tools. Use search_jmeter_docs to find documentation pages, and get_jmeter_page to read pages in full. Use convert_curl_or_har_to_jmx to convert one or more cURL commands or HAR JSON traces into valid Apache JMeter .jmx test plan XML (supporting GET, POST, PUT, DELETE, PATCH, and RFC 9838 QUERY methods). Use lint_jmx_snippet to validate JMX test plan snippets against performance best practices. Use calculate_workload_model to compute Little's Law concurrency, pacing, ramp-up, and JVM heap sizing. Use plan_distributed_testing to configure Master-Worker RMI ports, user.properties, firewall rules, and Docker manifests. Use tune_linux_os to generate sysctl.conf, limits.conf, and systemd tuning parameters for high-concurrency injectors. Use lookup_jmeter_property, get_jsr223_recipe, and lookup_error_playbook for precise configuration and troubleshooting guidance. Always cite the docs.jmeter.ai URL you used when answering.

Known tools 10

search_jmeter_docs

Search the Apache JMeter documentation on docs.

Inferred read-only

get_jmeter_page

Fetch the full markdown text of one docs.

Inferred read-only

lint_jmx_snippet

Validate a JMeter test plan XML string or snippet against best practices and performance anti-patterns (e.

Inferred read-only

calculate_workload_model

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.

Inferred read-only

lookup_jmeter_property

Search or lookup curated JMeter properties (e.

Inferred read-only

get_jsr223_recipe

Fetch production-ready, performant Groovy scripts for JMeter JSR223 samplers, preprocessors, and postprocessors (e.

Inferred read-only

lookup_error_playbook

Get immediate root causes, OS/JVM config fixes, and remediation steps for common JMeter exceptions (e.

Inferred read-only

plan_distributed_testing

Generate Master-Worker RMI port assignments, user.

Inferred read-only

tune_linux_os

Generate production sysctl.

Inferred read-only

convert_curl_or_har_to_jmx

Convert one or more cURL commands or HAR (HTTP Archive 1.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.jmeter-docs]
url = "https://docs.jmeter.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: jmeter-docs
Remote MCP URL: https://docs.jmeter.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "jmeter-docs",
  "transport": "streamable-http",
  "url": "https://docs.jmeter.ai/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.