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
      11 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

    • SmartBear MCP

      keybrdist
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with seamless access to SmartBear's suite of testing and monitoring tools, enabling querying testing data, analyzing performance metrics, and managing test automation through natural language.
      9,082 npm
      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.6/5.0

    Scored across 17 tools

    Disambiguation2/5

    Multiple tools have overlapping boundaries, particularly virtual_services_virtual_service and virtual_services_messaging_virtual_service, which share nearly identical action sets (deploy, stop, configure, assign_transactions, set_proxy, etc.) and the generic VS schema includes messaging fields. Additionally, blazemeter_account and blazemeter_user both deal with account/user information, creating potential confusion for an agent.

    Naming Consistency4/5

    Most tools follow a consistent '{domain}_{resource}' pattern with verb-based actions in snake_case (e.g., virtual_services_http_transaction.create, blazemeter_workspaces.list). Minor deviations include action names 'create-mq9' and 'update-mq9' using hyphens instead of underscores, and inconsistency in singular/plural resource names (blazemeter_account vs blazemeter_workspaces). Overall the pattern is predictable.

    Tool Count4/5

    With 17 tools covering both BlazeMeter platform entities (accounts, workspaces, user) and the service virtualization domain (services, transactions, virtual services, templates, configurations, assets, test data, recordings, sandbox, tracking, locations), the count is on the heavier side but appropriate for the broad scope. Each tool has a distinct resource focus, though some could be consolidated.

    Completeness2/5

    Significant gaps in lifecycle coverage: most entities (transactions, virtual services, templates, configurations, assets, recordings) lack delete operations, and actions can only be read/listed/created with no update/delete. Messaging virtual services also lack keystore/truststore assignment that the generic virtual service has. These gaps will cause agent failures when attempting full lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources