MCP / Developer tools
Blazemeter MCP: developer workflows
BlazeMeter is a continuous testing platform that enables users to create, run, and analyze performance and functional tests for web and mobile applications. Connect it to Claude, Codex, Cursor or any MCP client through one FlyMy.AI MCP.
$ YOUR NEXT RUN
Use Blazemeter MCP in your assistant
Paste this prompt into Claude Code, Codex, Cursor or any agent. It reads the guide and helps you connect.
Read https://flymy.ai/skill.md and https://flymy.ai/mcp/blazemeter.md. Help me connect Blazemeter MCP to this assistant. Then help me run this task: Use Blazemeter to create api monitoring schedule. Ask me for the required inputs first and show the result.
What Blazemeter MCP can do
20 actions in the FlyMy.AI catalog, the most used first. Your agent finds them through search_tools and calls the one the task needs.
| Action | What it does |
|---|---|
# BLAZEMETER_CREATE_API_MONITORING_SCHEDULE | Create a new schedule for running api monitoring tests. |
# BLAZEMETER_CREATE_MULTI_TEST | Create a new multi-test within a specified project. |
# BLAZEMETER_CREATE_PROJECT | Create a new project. |
# BLAZEMETER_CREATE_TEST | Create a new single test within a specified project. |
# BLAZEMETER_DELETE_API_MONITORING_SCHEDULE | Delete a specific test schedule by its id. |
# BLAZEMETER_GET_ACCOUNTS | Retrieve a list of accounts associated with the authenticated user. |
# BLAZEMETER_GET_API_MONITORING_SCHEDULE | Retrieve details of a specific api monitoring schedule by its id. |
# BLAZEMETER_GET_API_MONITORING_SCHEDULES | Retrieve a list of all test schedules in your account. |
# BLAZEMETER_GET_MULTI_TEST | Retrieve details of a specific multi-test. |
# BLAZEMETER_GET_MULTI_TESTS | Retrieve a list of multi-tests within a specified project or workspace. |
# BLAZEMETER_GET_PROJECTS | Retrieve a list of projects within a specified workspace. |
# BLAZEMETER_GET_TESTS | Retrieve a list of single tests within a specified project or workspace. |
Show all 20 actions
| Action | What it does |
|---|---|
# BLAZEMETER_GET_TEST_VALIDATIONS | Retrieve validation results for a specific test by its id. |
# BLAZEMETER_GET_USER | Retrieve information about the authenticated user. |
# BLAZEMETER_GET_WORKSPACES | Retrieve a list of workspaces for a specified account. |
# BLAZEMETER_STOP_MASTER | Stop a specific test execution (master) by its id. |
# BLAZEMETER_UPDATE_API_MONITORING_SCHEDULE | Update the configuration of an existing api monitoring schedule. |
# BLAZEMETER_UPDATE_TEST | Update details of a specific test by its id. |
# BLAZEMETER_UPLOAD_TEST_FILES | Upload files to a specific test by its id. |
# BLAZEMETER_VALIDATE_TEST | Validate a specific test by its id. |
Ask your agent
Requests to paste as they are. Each one runs on the actions named under it.
BLAZEMETER_CREATE_API_MONITORING_SCHEDULEBLAZEMETER_CREATE_MULTI_TESTBLAZEMETER_CREATE_PROJECTConnect Blazemeter in a minute
One MCP for every integration. Add it once, then every MCP in the catalog is a request away.
- 01
Add FlyMy.AI
Add the FlyMy.AI MCP to your assistant with one of the commands below and sign in. No key to copy.
- 02
Add your Blazemeter credentials
Paste them into the Blazemeter connection settings once; they stay with FlyMy.AI, never in a prompt or a chat.
- Account ID - The Account ID used for authentication. Get API key →
- API Key ID - The API Key ID used for authentication. Get API key →
- API Key Secret - The API Key Secret used for authentication. Get API key →
- 03
Ask
Paste a request from this page. Every run shows what it cost.
claude mcp add --transport http flymyai https://mcp-agents.flymy.ai/mcp
Then run /mcp in Claude Code and sign in.
codex mcp add flymy --url https://mcp-agents.flymy.ai/mcp
Then run codex mcp login flymy to sign in.
https://mcp-agents.flymy.ai/mcp
Settings, Connectors, Add custom connector: paste this URL.
Pay per run
FlyMy.AI bills the run: the model and the tool's seconds. Calls go to your own Blazemeter account, under its plan and limits. No seats and no minimum.
Go to the source
From the FlyMy.AI platform catalog of 2026-11-03: name, description, actions and setup as the platform lists them. Examples are requests to paste, not recorded runs.