Blazemeter
BlazeMeter is a continuous testing platform that enables users to create, run, and analyze performance and functional tests for web and mobile applications.
Verdict
Common use cases
- Schedule API health checks before releases
- Create load tests during sprint planning
- Retrieve test results when debugging incidents
- Audit active monitoring schedules across projects
- Initialize new projects for QA environments
Integration
- Vendor
- Blazemeter
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 20
- Composio slug
blazemeter
Tools
- Create API Monitoring Schedule
Tool to create a new schedule for running api monitoring tests. use when you need to automate test runs at defined intervals after determining the correct cron expression and test or collection id.
- Create Multi Test
Tool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."
- Create Project
Tool to create a new project. use when you need to initialize a project in a specific workspace. use after confirming the workspace id.
- Create Test
Tool to create a new single test within a specified project. use when registering a new performance test via api.
- Delete API Monitoring Scheduledestructive
Tool to delete a specific test schedule by its id. use when you need to remove a scheduled test by its unique schedule identifier.
- Get Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
- Get API Monitoring Schedule
Tool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.
- Get API Monitoring Schedules
Tool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.
- Get Multi Test
Tool to retrieve details of a specific multi-test. use after creating or listing multi-tests when you need full configuration and status. minimal example: "get multi-test 12345678 with populated tests."
- Get Multi Tests
Tool to retrieve a list of multi-tests within a specified project or workspace. use when you need to enumerate available multi-tests by specifying a project or workspace id.
- Get Projects
Tool to retrieve a list of projects within a specified workspace. use when you need to enumerate or page through projects under a given workspace.
- Get Tests
Tool to retrieve a list of single tests within a specified project or workspace. use when you need to list tests after organizing them. example: "get tests for projectid=prj-5678".
- Get Test Validations
Tool to retrieve validation results for a specific test by its id. use after uploading or modifying test files to confirm file validation status.
- Get User
Tool to retrieve information about the authenticated user. use when you need the current user's profile and have valid authentication.
- Get Workspaces
Tool to retrieve a list of workspaces for a specified account. use when you need to list or filter workspaces by account, status, or name.
- Stop Master
Tool to stop a specific test execution (master) by its id. use when you need to abort a running test.
- Update API Monitoring Schedule
Tool to update the configuration of an existing api monitoring schedule. use when you need to enable or disable a schedule after confirming its id.
- Update Test
Tool to update details of a specific test by its id. use when you need to modify test configuration or name of an existing test after confirming its id. example: "update the test name to 'loadtest' for test with id '12345'."
- Upload Test Files
Tool to upload files to a specific test by its id. use after creating or selecting a test to attach scripts or resources before execution.
- Validate Test
Tool to validate a specific test by its id. use after creating or updating a test to ensure its configuration is valid.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find BlazeMeter in the MCP directory and click Connect. 3. You'll be redirected to BlazeMeter's OAuth consent screen — sign in with your BlazeMeter account. 4. Grant Switchy permission to read and manage tests, projects, schedules, and account data (the scopes cover test creation, schedule management, and result retrieval). 5. After authorizing, you'll return to Switchy and see BlazeMeter listed as connected. 6. Open any Space and type '@BlazeMeter get accounts' to confirm the connection works — you should see a list of your BlazeMeter accounts. 7. To create a test, use '@BlazeMeter create test' followed by project ID and test parameters; to schedule monitoring, use '@BlazeMeter create api monitoring schedule' with a cron expression and test ID.
What teammates see: by default, memories from Blazemeter are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Accounts
@BlazeMeter get accounts. Show me all accounts associated with my authenticated user so I can confirm which workspaces are available.Open in a Space →
Create Load Test
@BlazeMeter create test in project 12345 named 'checkout-flow-load-test'. Set it up so we can run load against the staging checkout API.Open in a Space →
Schedule API Monitor
@BlazeMeter create api monitoring schedule for test 67890 to run every hour using cron '0 * * * *'. We need continuous monitoring on the payment gateway.Open in a Space →
Review Active Schedules
@BlazeMeter get api monitoring schedules. Show me every active schedule so I can see what's currently running and when.Open in a Space →
Initialize New Project
@BlazeMeter create project named 'mobile-api-tests' in workspace 54321. We're spinning up a new test suite for the mobile backend.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@blazemeter list all my scheduled API monitoring tests and show me which ones run most frequently
Found 7 active API monitoring schedules in your account. The most frequent is 'Checkout Flow Health Check' running every 5 minutes (cron: */5 * * * *), followed by 'Payment Gateway Uptime' every 15 minutes. Three schedules run hourly: 'Search API Latency', 'User Auth Endpoint', and 'Inventory Sync'. Two run daily at 3 AM UTC: 'Full Regression Suite' and 'Third-Party Integration Tests'. All schedules are currently enabled and last executed within their expected windows.
This example demonstrates read-only enumeration of test schedules. The MCP requires OAuth2 authentication with read access to your BlazeMeter account. Response reflects your actual schedule configuration — accounts with no schedules will return an empty list. Useful for auditing test coverage before adding new monitors.
@blazemeter create a new multi-test called 'Black Friday Load Simulation' in project 8472 that combines our checkout and inventory tests
Created multi-test 'Black Friday Load Simulation' (ID: mt-9384) in project 8472. This multi-test is now available for configuration but does not yet include test scenarios. Next steps: add your checkout and inventory test IDs to this multi-test container, configure load distribution percentages, and set ramp-up parameters. You can run this multi-test on-demand or schedule it once configured. The test appears in your BlazeMeter dashboard under project 8472.
This write operation creates a container for combining multiple performance tests but does not automatically populate it with test scenarios. You must have write permissions on the specified project, and the project ID must exist in your workspace. Creating a multi-test does not trigger any test execution or incur load generation costs until you explicitly run it.
@blazemeter review my account structure and suggest which workspace I should use for a new mobile app performance testing project
Your BlazeMeter account has 3 workspaces: 'Production Monitoring' (12 active projects, mostly API monitors), 'QA Performance' (8 projects, mix of load tests and functional tests), and 'Experimental' (2 projects, last activity 4 months ago). For a new mobile app performance project, 'QA Performance' is the best fit — it already contains mobile-related projects like 'iOS Checkout Flow' and 'Android API Client Tests', and the team has established naming conventions (app-platform-feature pattern). The workspace has 15 available test slots and recent activity indicates active maintenance.
This synthesis example combines account enumeration with AI reasoning to provide workspace recommendations. The MCP retrieves workspace and project metadata, then the AI analyzes patterns to guide decision-making. Recommendations depend on your actual account structure — new accounts with minimal history will receive different guidance. This does not create or modify any resources.
Use-case deep-dives
When this MCP fits teams running scheduled performance checks
A 6-person platform team runs nightly load tests against staging before each sprint demo. The Blazemeter MCP handles this well: you authenticate once via OAuth2, then use Create API Monitoring Schedule to set cron-based test runs and Get API Monitoring Schedules to audit what's queued. The 20-tool scope covers project setup (Create Project, Create Test) and schedule lifecycle without manual portal clicks. This works cleanly if your test definitions are stable and you're scheduling fewer than 30 distinct test suites—beyond that, the schedule-list calls get noisy and you'll want a dedicated CI orchestrator instead. If your team already lives in Slack or a shared workspace and just needs to kick off tests or check results without context-switching to Blazemeter's UI, this MCP closes the loop.
When you need API test triggers tied to deploy events
A 3-person SaaS startup deploys to production 4-6 times a week and wants smoke tests to fire immediately after each deploy, not on a fixed schedule. The Blazemeter MCP's Create Test and Create Multi Test tools let you script test creation from a deploy webhook, but the MCP doesn't expose a synchronous 'run now' trigger—you're still scheduling or manually starting tests in the portal. If your deploy pipeline already calls Blazemeter's REST API directly, this MCP adds OAuth2 convenience but doesn't unlock new automation. It's a fit if you're building a Switchy workflow where a human reviews deploy logs and then says 'run the smoke suite'—the MCP handles the API call in natural language. For fully headless post-deploy testing, stick with Blazemeter's native API or a CI plugin.
When support needs read-only test visibility without portal access
A 10-person support team fields customer complaints about slow API responses and wants to check if recent load tests caught the regression. The Blazemeter MCP's Get API Monitoring Schedules and Get Accounts tools give read access to test history and account structure, so a support agent can ask 'show me the last 5 API monitoring runs' without needing a Blazemeter login. This works if your test naming convention is clear and your schedule count is under 50—otherwise, parsing the schedule list in a chat interface gets messy. The MCP doesn't surface test results or metrics directly (those require separate API calls or the portal), so this is useful for 'did we test this endpoint recently' questions, not 'what was the p95 latency'. If your support team just needs test existence checks and schedule audits, this MCP keeps them out of the Blazemeter UI.
Frequently asked
What does the Blazemeter MCP let me do in Switchy?
It lets your team create and manage performance tests, multi-tests, and API monitoring schedules directly from Switchy's AI workspace. You can spin up new projects, configure test runs with cron expressions, retrieve account details, and delete schedules — all without leaving the conversation. It's useful when you want to automate load testing workflows or inspect existing test configurations without opening the Blazemeter dashboard.
Do I need admin access to connect Blazemeter via OAuth?
You need an account with permissions to create projects and tests in your Blazemeter workspace. The OAuth flow will ask for scopes that cover reading accounts, creating tests, and managing schedules. If you're only a viewer in Blazemeter, the connection will succeed but most tools will fail when you try to create or delete resources. Check with your Blazemeter admin if you're unsure about your role.
Can the MCP run a performance test immediately or only schedule it?
It can create and schedule tests but doesn't trigger an immediate run. You'll use tools like Create API Monitoring Schedule to set up recurring test runs with a cron expression, or Create Test to register a new test configuration. To execute a test on demand, you still need to go into the Blazemeter UI or use their separate test execution API endpoints, which this MCP doesn't expose.
How is this different from just using the Blazemeter API directly?
The MCP wraps 20 common Blazemeter API calls so your team can manage tests conversationally in Switchy instead of writing curl commands or scripts. It's faster for ad-hoc tasks like "create a multi-test in project 12345" or "list all my schedules". If you need advanced endpoints or custom workflows, you'll still want the full API. The MCP is about speed and shared context, not replacing your CI pipeline.
Who on the team should connect this MCP?
Whoever owns your performance testing setup and has create/delete permissions in Blazemeter. That's usually a QA lead, DevOps engineer, or backend developer who already manages test projects. Once connected in Switchy, the whole team can ask questions about test schedules or trigger new test creation, but the OAuth token belongs to the person who authenticated — so their Blazemeter permissions apply to every action.