Add jmeter mcp plugin

[diego-ferrand]

No description provided.

[undera]

The plugin id is bzm-mcp-v1. IDs are permanent identifiers and are not meant to carry a version; versions belong in the versions map. Could you confirm the -v1 suffix is intentional, or change it to a more generic ID?

[diego-ferrand]

The ID is bzm-mcp-v1 because this plugin implements only MCP 1.x. MCP 2.x will be a separate plugin, bzm-mcp-v2, allowing both versions to be installed side by side.

Both plugins use the official MCP Java SDK, which handles the wire protocol. However, MCP 1.x and 2.x use different session models. Keeping them separate allows us to fix or implement features independently for each version. It also avoids potential conflicts between the the SDK versions.

• MCP 1.x uses a stateful, handshake-based protocol. This includes the specification dated 2025-11-25 and all earlier revisions. The 1.x SDKs establish a persistent session and require an initialization handshake before any other calls. This plugin is built on that SDK line.
• MCP 2.x introduced a stateless protocol in the specification dated 2026-07-28. The official SDKs moved to version 2.0.0 for this change, removing both the initialization handshake and protocol-level sessions.

A server that supports only the 2026-07-28 specification will reject this plugin's initialization handshake. Updating the existing plugin under the same Plugins Manager ID would risk replacing a working MCP 1.x client with an incompatible implementation.

Using separate IDs keeps the existing 1.x plugin stable while providing a path for the 2.x implementation.