plan_distributed_testing — JMeter Docs MCP Tool
plan_distributed_testing
(plan distributed testing) is one of 10 tools on the
JMeter Docs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_distributed_testing from your client
- Claude Code JMeter Docs plan_distributed_testing run in your project directory
- Claude Desktop JMeter Docs plan_distributed_testing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor JMeter Docs plan_distributed_testing ~/.cursor/mcp.json
- VS Code JMeter Docs plan_distributed_testing .vscode/mcp.json
- Zed JMeter Docs plan_distributed_testing ~/.config/zed/settings.json
- Windsurf JMeter Docs plan_distributed_testing ~/.codeium/windsurf/mcp_config.json
- Cline JMeter Docs plan_distributed_testing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI JMeter Docs plan_distributed_testing ~/.gemini/settings.json
- Grok JMeter Docs plan_distributed_testing .mcp.json (in your project root)
- ChatGPT JMeter Docs plan_distributed_testing Settings → Connectors → Advanced → Developer mode
- Claude.ai JMeter Docs plan_distributed_testing Settings → Connectors → Add custom connector
- LangChain JMeter Docs plan_distributed_testing pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jmeter-docs https://docs.jmeter.ai/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.