BlazeMeter API Test MCP Server

The BlazeMeter API Test MCP Server connects AI tools directly to cloud-based BlazeMeter API Testing & Monitoring platform (Runscope). It enables AI assistants, agents, and chat-based tools to interact with BlazeMeter API test resources through the Model Context Protocol (MCP).

By using this MCP server, you can query API testing data, manage test assets, analyze results, and automate testing workflows using natural language interactions.

What you can do with BlazeMeter API Test MCP Server

Use the BlazeMeter API Test MCP Server to:

  • Access teams and organizational context within your BlazeMeter account

  • Manage API testing assets such as buckets, tests, steps, and environments

  • Execute API tests and retrieve execution results

  • Create and manage test schedules

  • Integrate BlazeMeter API testing data into MCP‑compatible AI tools and workflows

Prerequisites

Before you set up the BlazeMeter API Test MCP Server, ensure that you have:

  • A BlazeMeter API Monitoring access token

  • A compatible MCP host (for example, VS Code, Claude Desktop, Cursor, or Windsurf)

  • Docker (required only for Docker-based deployment)

  • uv (a high-performance Python package) and Python 3.11+ (required only for installation from source code)

  • Account owner consent for AI-assisted features. For more information, see Manage AI Consent.

Installation

You can deploy the BlazeMeter API Test MCP Server locally.

The installation options are as follows:

  • Interactive CLI configuration

  • Manual client configuration using a binary

  • Manual client configuration from remote source code

  • Docker-based configuration

Configure an MCP client using the interactive CLI tool

The simplest way to configure your MCP client is using the interactive CLI tool:

  1. From the Releases page, download the appropriate binary file for your operating system. Select the binary that matches your OS (Windows, macOS, Linux).

  2. Run the binary to launch the interactive configuration tool.

The tool automatically generates the MCP JSON Key configuration for you.

For macOS, you may encounter a security alert "Apple could not verify 'mcp-bzm-apitest-darwin' is free of malware." If this occurs, allow the binary to run from System Settings > Privacy & Security, and then rerun it.

Configure an MCP client manually (binary installation)

  1. From the Releases page, download the binary for your operating system.

  2. Add the following configuration to your MCP client:

Copy 
{
  "mcpServers": {
    "BlazeMeter API Test MCP": {
      "command": "/path/to/mcp-bzm-apitest-binary",
      "args": ["--mcp"],
      "env": {
        "BZM_API_TEST_TOKEN_FILE": "/path/to/your/bzm_api_test_token.env"
      }
    }
  }
}

Configure an MCP client manually (from remote source code)

  1. Install uv and Python 3.11+.

  2. Configure your MCP client as follows:

Copy 
{
  "mcpServers": {
    "BlazeMeter API Test MCP": {
      "command": "uvx",
      "args": [
        "--from", "git+https://github.com/Runscope/mcp-bzm-apitest.git@v1.0.0",
        "-q", "mcp-bzm-apitest", "--mcp"
      ],
      "env": {
        "BZM_API_TEST_TOKEN_FILE": "/path/to/your/bzm_api_test_token.env"
      }
    }
  }
}

The uvx installs and runs the package and its dependencies in a temporary environment.

You can change to any version that has been released or any branch you want. Package support for uvx command is supported from version 1.0.1 onwards. For more information on the uv/uvx arguments used, see the official uv documentation.

Configure an MCP client for Docker

Use the following MCP configuration to run the server in Docker:

Copy 
{
  "mcpServers": {
    "Docker BlazeMeter API Test MCP": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BZM_API_TEST_TOKEN=your_api_token",
        "ghcr.io/blazemeter/mcp-bzm-apitest:latest"
      ]
    }
  }
}

Configure custom CA certificates for Docker (corporate environments)

Use custom Certificate Authority (CA) certificates in Docker when one or more of the following conditions apply:

  • Your organization uses self-signed certificates

  • You're behind a corporate proxy that performs SSL inspection

  • Your environment includes a custom CA

  • You encounter SSL certificate verification errors during test execution

Custom CA certificate bundles require the following configuration:

  • Certificate Volume Mount: Mount your custom CA certificate bundle into the container

  • SSL_CERT_FILE Environment Variable: Explicitly set the SSL_CERT_FILE environment variable to point to the certificate location inside the container

Example configuration:

Copy 
{
  "mcpServers": {
    "Docker BlazeMeter API TEST MCP": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "SSL_CERT_FILE=/etc/ssl/certs/custom-ca-bundle.crt",
        "-e",
        "BZM_API_TEST_TOKEN=your_api_token",
        "ghcr.io/blazemeter/mcp-bzm-apitest:latest"
      ]
    }
  }
}

In the above example, replace:

  • /path/to/your/ca-bundle.crt with your host system's CA certificate file path

  • The container path /etc/ssl/certs/custom-ca-bundle.crt with any path you prefer (ensure it matches SSL_CERT_FILE)

The SSL_CERT_FILE environment variable must be set to point to your custom CA certificate bundle. The httpx library automatically respects the SSL_CERT_FILE environment variable for SSL certificate verification.

Server tools

The following tools are available with the BlazeMeter API Test MCP server.

  • blazemeter_apitest_teams

    • List teams within your BlazeMeter account

    • Read team details

    • Get a list of all team users

  • blazemeter_apitest_buckets

    • List all the buckets

    • Read bucket details

    • Create a new bucket

  • blazemeter_apitest_tests

    • List all API tests within a bucket

    • Read test details

    • Create a new API test

    • Get the test metrics

  • blazemeter_apitest_schedules

    • List all schedules within a test

    • Read schedule details

    • Create a new schedule

  • blazemeter_apitest_steps

    • List all steps within a test

    • Read test step details

    • Add a new Pause and Request step (with URL, Method, Body and Assertions) to a test

  • blazemeter_apitest_environments

    • List all test environments

    • Read test environment details

  • blazemeter_apitest_results

    • Execute an individual test or all bucket-level tests

    • List last 50 test results

    • Read test result and bucket-level result details

Support and licensing

This project is licensed under the Apache License, Version 2.0.

To ensure the security of your MCP clients, never share API tokens, use the token in an .env file rather than directly in environment variables, and keep your .env files secure and private.