BlazeMeter Functional MCP integration for AI agents.
Connect AI agents to BlazeMeter Functional through 3 structured actions, including get active sessions, get multi test, and list multi tests. Review authenti…
- ACTION CONTRACTS
- 3
- 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 Functional integration exposes
The BlazeMeter Functional Agent App exposes 3 provider-backed actions for developer tools work. Its current contract lets an authorized agent get the active blazemeter sessions for the configured api key, get one blazemeter functional multi-test by collection id, and list blazemeter functional multi-tests in a workspace. 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 Functional account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BlazeMeter Functional capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_active_sessionsREADGet the active BlazeMeter sessions for the configured API key.
get_multi_testREADGet one BlazeMeter Functional multi-test by collection ID.
INPUTS: collectionId / populateTests
list_multi_testsREADList BlazeMeter Functional multi-tests in a workspace.
INPUTS: workspaceId / projectId / skip / limit / sort
INPUT CONTRACTS
Know what the action needs before it runs.
get_multi_test
collectionIdREQUIRED- The BlazeMeter multi-test collection ID to retrieve.
populateTestsOPTIONAL- Whether BlazeMeter should include embedded test objects.
list_multi_tests
workspaceIdREQUIRED- The BlazeMeter workspace ID to list multi-tests from.
projectIdOPTIONAL- The BlazeMeter project ID used to filter multi-tests.
skipOPTIONAL- The number of multi-tests to skip before returning results.
limitOPTIONAL- The maximum number of multi-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 Active Sessions
Get the active BlazeMeter sessions for the configured API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_active_sessionsVerify with Get Multi Test
Get one BlazeMeter Functional multi-test by collection ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_multi_testSAFETY BOUNDARY
Operate BlazeMeter Functional with explicit limits
- Authorize BlazeMeter Functional with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BlazeMeter Functional 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 Functional rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BlazeMeter Functional 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
- 3
- 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 Functional.