BlazeMeter Performance MCP integration for AI agents.
Connect AI agents to BlazeMeter Performance through 6 structured actions, including get test, get user, and list accounts. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BlazeMeter Performance integration exposes
The BlazeMeter Performance Agent App exposes 6 provider-backed actions for developer tools work. Its current contract lets an authorized agent get one blazemeter performance test by id, get the blazemeter user profile associated with the configured api key, and list blazemeter accounts available to the configured api key. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BlazeMeter Performance account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BlazeMeter Performance capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_testREADGet one BlazeMeter performance test by ID.
INPUTS: testId
get_userREADGet the BlazeMeter user profile associated with the configured API key.
list_accountsREADList BlazeMeter accounts available to the configured API key.
INPUTS: skip / limit / sort
list_projectsREADList BlazeMeter projects for a workspace.
INPUTS: workspaceId / skip / limit / sort
list_testsREADList BlazeMeter performance tests by workspace or project.
INPUTS: workspaceId / projectId / skip / limit / sort
list_workspacesREADList BlazeMeter workspaces for an account.
INPUTS: accountId / enabled / textFilter
INPUT CONTRACTS
Know what the action needs before it runs.
get_test
testIdREQUIRED- The BlazeMeter test ID to retrieve.
list_accounts
skipOPTIONAL- The number of records to skip before returning results.
limitOPTIONAL- The maximum number of records to return.
sortOPTIONAL- Sort fields accepted by BlazeMeter, such as name or -created.
list_projects
workspaceIdREQUIRED- The BlazeMeter workspace ID to list projects from.
skipOPTIONAL- The number of projects to skip before returning results.
limitOPTIONAL- The maximum number of projects to return.
sortOPTIONAL- Sort fields accepted by BlazeMeter, such as name or -created.
list_tests
workspaceIdOPTIONAL- The BlazeMeter workspace ID used to filter tests.
projectIdOPTIONAL- The BlazeMeter project ID used to filter tests.
skipOPTIONAL- The number of tests to skip before returning results.
limitOPTIONAL- The maximum number of tests to return.
sortOPTIONAL- Sort fields accepted by BlazeMeter, such as name or -created.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Test
Get one BlazeMeter performance test by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_testVerify with Get User
Get the BlazeMeter user profile associated with the configured API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_userSAFETY BOUNDARY
Operate BlazeMeter Performance with explicit limits
- Authorize BlazeMeter Performance with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BlazeMeter Performance data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BlazeMeter Performance rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BlazeMeter Performance task completed successfully.
CONNECTION MODEL
API key
BlazeMeter API secret used as the Basic Auth password. Create or copy API keys from the BlazeMeter API Keys settings page: https://a.blazemeter.com/app/#/settings/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BlazeMeter Performance.