🚀 JMeter MCP Server

Created By
QAInsightsa year ago
✨ JMeter Meets AI Workflows: Introducing the JMeter MCP Server! 🤯
Overview

What is JMeter MCP Server?

JMeter MCP Server is a Model Context Protocol (MCP) server that enables the execution of JMeter tests through MCP-compatible clients, integrating AI workflows with performance testing.

How to use JMeter MCP Server?

To use the JMeter MCP Server, install the necessary dependencies, ensure JMeter is accessible, and connect to the server using an MCP-compatible client. You can then send commands to execute JMeter tests.

Key features of JMeter MCP Server?

  • Execute JMeter tests in non-GUI mode for better performance.
  • Launch JMeter in GUI mode when needed.
  • Capture and return execution output for analysis.

Use cases of JMeter MCP Server?

  1. Automating performance testing workflows.
  2. Integrating JMeter with AI tools for enhanced testing capabilities.
  3. Running tests in a CI/CD pipeline to ensure application performance.

FAQ from JMeter MCP Server?

  • Can I run JMeter tests without a GUI?

Yes! The JMeter MCP Server allows you to execute tests in non-GUI mode, which is recommended for performance.

  • What is the required setup for JMeter MCP Server?

You need to install JMeter and configure the server with the correct paths in the .env file.

  • Is JMeter MCP Server compatible with all JMeter versions?

It is designed to work with JMeter 5.6.3 and may require adjustments for other versions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QAInsights
Star
22
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago