A
licenseNot graded
qualityD
maintenanceA powerful MCP server for automated JMeter test generation and execution with Docker integration and comprehensive performance analysis.
16 npm
1
MIT
jmeter-mcp-server
by IAnjaniKr
Related Servers
Alternatives to jmeter-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that analyzes OpenAPI/Swagger REST API contracts and generates BDD Gherkin feature files and TypeScript Jest regression test scripts.-
- AlicenseAqualityFmaintenanceMCP server for API test case generation from Swagger/OpenAPI specs. Parses Swagger 2.0 and OpenAPI 3.x, generates test cases across 8 categories (positive, negative, boundary, auth, security, idempotency, pagination, business logic), and exports to Postman, TestRail, Allure, k6, pytest, Gherkin, and CSV. Supports internal corporate APIs with auth headers. Auto-saves export files to your working di1023 npm2MIT
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables executing and interacting with JMeter tests through MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.2-
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables execution of JMeter performance tests through AI assistants and MCP-compatible clients like Claude, Cursor, and Windsurf.2-
- AlicenseAqualityCmaintenanceAn MCP server that automatically discovers API endpoints from any codebase, generates and runs tests, and produces per-role QA audit reports in PDF and XLSX.10753 npmMIT
TDQS
B3.3/5.0
Scored across 13 tools
Disambiguation3/5
Most tools have clearly distinct purposes, but the three create_test_plan variants overlap, especially create_test_plan_from_api_source with sourceType=openapi and create_test_plan_from_openapi. The explicit routing hint in the OpenAPI tool description helps, but an agent still faces ambiguity about which creation tool to use.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern, such as add_http_sampler, update_thread_group, and generate_report. Even the longer create_test_plan_from_* names stay predictable and readable.
Tool Count4/5
Thirteen tools is within the appropriate range for a JMeter-focused server and covers creation, editing, execution, and reporting. The count is slightly higher than necessary because create_test_plan_from_openapi is largely redundant with create_test_plan_from_api_source.
Completeness3/5
The server covers the main JMeter workflow: create/read plans, add core elements, run tests, and generate reports. However, updates are limited to thread group settings; samplers, assertions, timers, and config elements can only be deleted and recreated, which is a notable gap for iterative test editing.
Maintenance
ActivityInactive
ResponsivenessNo issues