Performance-Test -java-
Un serveur MCP (Model Context Protocol) développé en Java pour tester les performances d'un autre client.
claude mcp add --transport stdio rayenmalouche-performance-test-mcp-server-java- java -cp target/classes com.dicovery.performance.mcp.test.server.PerformanceTestServer --stdio \ --env JAVA_TOOL_OPTIONS="Optional: additional Java options" \ --env DISCOVERY_INTECH_HOST="http://localhost:8072 (default client host)"
How to use
This MCP server is a Java-based performance testing tool designed to evaluate the Discovery Intech client. It exposes several built-in MCP testing capabilities, including running a single performance test, executing load tests with concurrent requests, analyzing results, monitoring API costs, and exporting results for reporting. The server can operate in STDIO mode (for MCP clients), in HTTP/SSE mode (for tests and inspection), and in a Streamable HTTP mode (for MCP Inspector workflows). To use STDIO, start the server in console mode so the MCP client can interact via standard input/output; for HTTP/SSE, launch the server to expose endpoints for test orchestration and streaming results. Each tool is documented with example JSON payloads that show the required fields and structure for requests.
How to install
Prerequisites:
- Java 21 or higher
- Maven 3.8+ (for compilation)
- Discovery Intech client running (default at http://localhost:8072)
Installation steps:
- Clone the repository: git clone <repository-url>
- Navigate to the project directory: cd performance-test-mcp-server-java
- Compile the project using Maven: mvn clean compile
- Run the server in STDIO mode (for MCP clients): mvn spring-boot:run -Dspring-boot.run.arguments="--stdio"
- Alternatively, run the server directly with the prebuilt classes (example): java -cp target/classes com.dicovery.performance.mcp.test.server.PerformanceTestServer --stdio
Notes:
- Ensure the Discovery Intech client is running at the expected default URL (http://localhost:8072).
- To switch to HTTP/SSE mode, start the server without the --stdio flag or with appropriate arguments for your setup.
Additional notes
Tips and common considerations:
- Ports used by default: HTTP/SSE 45451 and Health check 45451/api/health. If combining with other services, ensure these ports are available or adjust configuration as needed.
- If you encounter JSON parsing or timeout issues, verify that the Discovery Intech client is reachable and that the server has network access to the client endpoint.
- For debugging, enable verbose logging by setting Java logging properties (example: -Dlogging.level.com.dicovery=DEBUG).
- The README lists several MCP tools (run_performance_test, run_load_test, analyze_test_results, monitor_costs, benchmark_scenarios, export_results). Use the example JSON payloads in the README as templates when issuing requests via STDIO or HTTP endpoints.
- If deploying in a containerized environment, you may consider wrapping the command in a Docker image and exposing the appropriate ports for STDIO/HTTP as needed.
