Skip to main content
Glama
Blazemeter

BlazeMeter Service Virtualization MCP Server

Official
by Blazemeter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to BlazeMeter Service Virtualization MCP Server

No user-submitted related servers found.

    Related Servers

    • jmeter-mcp

      Realtyka
      F
      license
      Not graded
      quality
      C
      maintenance
      Integrates Apache JMeter with AI assistants to run and manage load tests through natural language. It enables users to execute test plans, parse results, inspect test structures, and compare performance metrics across different runs.
      -
    • Specmatic MCP Server by specmatic

      Specmatic MCP Serverofficial

      specmatic
      A
      license
      A
      quality
      D
      maintenance
      Exposes Specmatic's API contract testing, resiliency testing, and mocking capabilities to AI coding agents via natural language, enabling automated validation and simulation of API behaviors.
      3
      20 npm
      12
      MIT

    • perfsage-jmeter-mcp

      perfsage
      A
      license
      A
      quality
      A
      maintenance
      Enables LLM agents to run self-healing JMeter performance tests via natural language, from environment setup to capacity discovery and SLO verdict reporting.
      12
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource (transactions, services, locations, configurations, assets, recordings, tracking, sandbox), and the descriptions spell out when to use each. The main soft spots are the generic-looking `virtual_services_virtual_service` (transactional only) sitting next to `virtual_services_messaging_virtual_service` — both answer to "virtual service" — and `virtual_services_sandbox` overlapping with the `create_and_test` action inside the HTTP transaction tool. These are resolvable from the descriptions but require careful reading.

    Naming Consistency4/5

    Tool names follow a predictable `<prefix>_<resource>` snake_case pattern (virtual_services_* for the domain tools, blazemeter_* for the account/identity tools), so the set is easy to scan. Minor deviations exist: singular/plural mixing (`blazemeter_user`, `blazemeter_account` vs `blazemeter_workspaces`, `virtual_services_location` vs others), and the action vocabulary inside tools mixes underscores with hyphens (`create-mq9`, `update-mq9`).

    Tool Count4/5

    17 tools is on the heavy side, but each maps to a genuine, distinct entity in the service-virtualization domain (transactions, virtual services, templates, TDM datasets, recordings, assets, configurations, tracking, sandbox, plus account/workspace scaffolding). Some surface is duplicated between the transactional and messaging virtual service tools (deploy/stop/configure/set_proxy/assign_*), which inflates the count, but nothing feels arbitrary.

    Completeness3/5

    Read/list/create/update coverage is strong across nearly every resource, and lifecycle actions (deploy, stop, configure, assign/unassign, sandbox testing, tracking) are well covered. However, there is no delete operation anywhere in the surface — not for transactions, services, virtual services, templates, configurations, assets, or recordings — and `virtual_services_action` offers no update/delete for actions, leaving agents with dead ends when cleanup is required. Messaging transactions also have no sandbox path (documented, but still an asymmetry with HTTP).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources