jmeter-mcp-server
A powerful MCP server for automated JMeter test generation and execution with Docker integration and comprehensive performance analysis.
README
🎯 JMeter MCP Server
A powerful Model Context Protocol (MCP) server for automated JMeter test generation and execution with Docker integration and comprehensive performance analysis.
🌟 Overview
The JMeter MCP Server is a streamlined, production-ready testing solution that integrates with MCP-compatible clients (like Claude Desktop, VS Code) to generate sophisticated JMeter test plans and execute them automatically via Docker with comprehensive performance analysis.
🚀 Key Features:
- 2 Essential Tools: Streamlined for maximum efficiency
- Complete Docker Automation: Zero manual intervention required
- Multi-Format Reports: HTML, Markdown, and JSON outputs
- Interactive Visualizations: Chart.js powered performance charts
- Professional Analysis: Trend detection and bottleneck identification
- API & UI Testing: Support for both API and web interface testing
- Real-time Execution: Containerized JMeter with live results
🛠️ Core Tools
1. 🚀 generate_jmeter_script - Advanced Test Generation
Create comprehensive JMeter test plans with modern features:
Features:
- Multi-threaded load simulation with configurable patterns
- CSV data parameterization for data-driven testing
- Response correlation and extraction (JSON Path, Regex)
- Multiple timer types and realistic load patterns
- Custom headers, authentication, and session management
- Response assertions and comprehensive validations
- Automatic file generation to
output/directory
Example:
{
"testName": "API Performance Test",
"baseUrl": "https://api.example.com",
"threadGroup": {
"numThreads": 50,
"rampUpTime": 120,
"loops": 10
},
"requests": [
{
"name": "Login",
"method": "POST",
"path": "/auth/login",
"headers": { "Content-Type": "application/json" },
"body": "{\"username\":\"${username}\",\"password\":\"${password}\"}",
"extractors": [
{
"variableName": "authToken",
"jsonPath": "$.token"
}
],
"assertions": [
{
"type": "responseCode",
"value": "200"
}
]
}
],
"csvDataSet": {
"fileName": "users.csv",
"variableNames": "username,password",
"delimiter": ","
}
}
2. 🐳 execute_jmeter_script - Docker Execution Engine
Automatically execute JMeter tests in a containerized environment with comprehensive analysis:
Features:
- Docker Automation: Uses
justb4/jmeter:latestfor consistent execution - Volume Mounting: Seamless data exchange between host and container
- Resource Management: Configurable CPU and memory limits
- Performance Analysis: Multi-dimensional performance metrics
- HTML Reports: Interactive dashboards with Chart.js visualizations
- Trend Analysis: Automatic bottleneck detection and recommendations
- Multiple Formats: HTML, Markdown, and JSON reports
Example:
{
"jmxFile": "API_Performance_Test.jmx",
"generateReports": true,
"resourceAnalysis": true,
"cpuLimit": "2",
"maxMemory": "2g"
}
📊 Performance Analysis Features
The execution engine provides comprehensive performance analysis:
🎯 Key Metrics
- Response time statistics (min, max, average, percentiles)
- Throughput analysis (requests/second, bytes/second)
- Error rate tracking and categorization
- Resource utilization monitoring
- Load pattern analysis
📈 Interactive Reports
- HTML Dashboard: Interactive charts with Chart.js
- Trend Analysis: Performance trends over time
- Bottleneck Detection: Automatic issue identification
- Recommendations: AI-powered optimization suggestions
- Raw Data: JTL files for custom analysis
🎨 Visualization Types
- Line charts for response times over time
- Bar charts for throughput metrics
- Pie charts for error distribution
- Histograms for response time distribution
⚡ Quick Start
🖥️ Installation
# Clone the repository
git clone https://github.com/chandanvars/jmeter-mcp-server.git
cd jmeter-mcp-server
# Install dependencies
npm install
# Start the MCP server
npm start
🐳 Docker Requirements
Ensure Docker is installed and running on your system:
# Verify Docker installation
docker --version
docker pull justb4/jmeter:latest
🚀 Basic Usage
Generate a JMeter Test:
# Using the MCP tool
generate_jmeter_script({
"testName": "API Load Test",
"baseUrl": "https://httpbin.org",
"requests": [
{
"name": "Get Request",
"method": "GET",
"path": "/get"
}
]
})
Execute the Test:
# Using the MCP tool
execute_jmeter_script({
"jmxFile": "API_Load_Test.jmx",
"generateReports": true
})
🏗️ Architecture
graph TB
subgraph "User Layer"
USER[👤 User]
CLAUDE[🤖 Claude Desktop]
VSCODE[📝 VS Code]
API[🔗 API Client]
end
subgraph "MCP Server"
SERVER[🏗️ MCP Server]
TOOL1[⚡ generate_jmeter_script]
TOOL2[🐳 execute_jmeter_script]
HANDLER[🎯 JMeter Handler]
end
subgraph "Docker Engine"
DOCKER[🐳 Docker]
JMETER[⚙️ JMeter Runtime]
VOLUMES[🔗 Volume Mounts]
end
subgraph "Analysis Engine"
PARSER[📊 JTL Parser]
ANALYZER[📈 Stats Analyzer]
GENERATOR[📋 Report Generator]
end
subgraph "Report Outputs"
HTML[🌐 HTML Report]
MD[📝 Markdown]
JSON[📊 JSON Data]
DASHBOARD[📈 JMeter Dashboard]
end
USER --> SERVER
SERVER --> TOOL1
SERVER --> TOOL2
TOOL2 --> DOCKER
DOCKER --> JMETER
JMETER --> PARSER
PARSER --> ANALYZER
ANALYZER --> GENERATOR
GENERATOR --> HTML
GENERATOR --> MD
GENERATOR --> JSON
JMETER --> DASHBOARD
📁 Project Structure
jmeter-mcp-server/
├── 📁 src/ # Source code
│ ├── 🚀 index.js # MCP server entry point
│ ├── 📁 handlers/ # Request handlers
│ │ └── 🎯 jmeterHandler.js # Core JMeter logic
│ └── 📁 utils/ # Utility functions
│ ├── 📂 fileWriter.js # File operations
│ └── 📝 promptGenerator.js # Prompt utilities
├── 📁 output/ # Generated JMX files
├── 📁 sample_data/ # Test data files
├── 📁 jmeter-results/ # Test execution results
│ ├── 🌐 performance-analysis.html
│ ├── 📝 performance-analysis.md
│ ├── 📊 performance-analysis.json
│ └── 📁 reports/ # JMeter dashboards
├── 🐳 docker-entrypoint.sh # Docker execution script
├── 📄 ARCHITECTURE.mermaid # System architecture
├── 📋 package.json # Project configuration
└── 📖 README.md # This file
🔧 Configuration
Environment Variables
NODE_ENV=production # Environment mode
PORT=3000 # HTTP server port
DEBUG=true # Enable verbose logging
Docker Configuration
The server automatically configures Docker execution with:
- Image:
justb4/jmeter:latest - Volume Mounts: Automatic mapping of test files and results
- Resource Limits: Configurable CPU and memory allocation
- Network: Bridge networking for external API access
📊 Generated Reports
HTML Interactive Dashboard
- Real-time Charts: Response times, throughput, errors
- Interactive Navigation: Drill-down capabilities
- Performance Trends: Time-based analysis
- Export Options: PNG, CSV, PDF
Markdown Documentation
- Executive Summary: Key performance indicators
- Detailed Analysis: Comprehensive metrics breakdown
- Recommendations: Performance optimization suggestions
- Historical Comparison: Trend analysis over time
JSON Machine Data
- Raw Metrics: All performance data in JSON format
- API Integration: Easy integration with monitoring tools
- Custom Analysis: Data for custom reporting tools
- Automation: Machine-readable for CI/CD pipelines
🚀 Advanced Examples
API Testing with Authentication
{
"testName": "Authenticated API Test",
"baseUrl": "https://api.github.com",
"threadGroup": {
"numThreads": 10,
"rampUpTime": 30,
"loops": 5
},
"requests": [
{
"name": "Get User Profile",
"method": "GET",
"path": "/user",
"headers": {
"Authorization": "Bearer ${token}",
"Accept": "application/vnd.github+json"
},
"assertions": [
{
"type": "responseCode",
"value": "200"
},
{
"type": "jsonPath",
"value": "$.login"
}
]
}
],
"csvDataSet": {
"fileName": "github_tokens.csv",
"variableNames": "token"
}
}
UI Testing Workflow
{
"testName": "E-commerce UI Flow",
"baseUrl": "https://demo.opencart.com",
"threadGroup": {
"numThreads": 5,
"rampUpTime": 60,
"loops": 3
},
"requests": [
{
"name": "Homepage",
"method": "GET",
"path": "/",
"assertions": [
{
"type": "containsText",
"value": "OpenCart"
}
]
},
{
"name": "Product Search",
"method": "GET",
"path": "/index.php?route=product/search&search=macbook",
"assertions": [
{
"type": "responseTime",
"value": "3000"
}
]
}
]
}
🔧 Development
Setup for Development
# Clone and install
git clone https://github.com/chandanvars/jmeter-mcp-server.git
cd jmeter-mcp-server
npm install
# Run in development mode
npm run dev
# Run tests
npm test
Available Scripts
npm start # Start MCP server
npm run dev # Development mode with debugging
npm test # Run test suite
npm run clean # Clean output directories
📚 Examples & Documentation
- Basic Usage: Simple API testing examples
- Advanced Scenarios: Complex multi-step workflows
- Performance Testing: Load testing best practices
- UI Testing: Web application testing patterns
- Authentication: Various auth method examples
🤝 Contributing
We welcome contributions! Please:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
🆘 Support
For support and questions:
🗺️ Roadmap
Current Version Features
- ✅ Streamlined Architecture: 2 essential tools
- ✅ Complete Docker Automation: Zero manual intervention
- ✅ Multi-Format Reports: HTML, Markdown, JSON
- ✅ Interactive Dashboards: Chart.js visualizations
- ✅ Performance Analysis: Comprehensive metrics
- ✅ Architecture Documentation: Mermaid diagrams
Future Enhancements
- [ ] WebSocket Testing: Real-time connection testing
- [ ] GraphQL Support: Native GraphQL test generation
- [ ] Database Testing: SQL performance testing
- [ ] Cloud Integration: AWS/Azure monitoring
- [ ] CI/CD Templates: Pipeline integration examples
- [ ] Mobile Testing: Mobile app performance testing
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
- Apache JMeter Team - For the incredible testing framework
- Model Context Protocol - For the communication standard
- Docker Community - For containerization technology
- Chart.js Team - For beautiful visualizations
- Testing Community - For feedback and contributions
🎯 Made with ❤️ for the testing community by Chandan Varshney
Automated JMeter testing with Docker integration and professional performance analysis!
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。