# How to connect Blazemeter to OpenClaw (paste one key, 92 tools) > Connect Blazemeter to OpenClaw with ClawLink: paste your Blazemeter key once and 92 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/blazemeter The usual route to Blazemeter access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Blazemeter setup: install one ClawHub skill, connect Blazemeter in the browser, and OpenClaw can call real Blazemeter actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Blazemeter. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Blazemeter** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect blazemeter # connect Blazemeter (browser OAuth) npx -y @useclawlink/cli actions blazemeter # list available actions npx -y @useclawlink/cli run blazemeter --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Blazemeter in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your Blazemeter account details once. Verify the connection by asking OpenClaw: > Use Blazemeter to convert transactions and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Blazemeter is connected in the dashboard, that agent calls the same 92 Blazemeter tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Blazemeter MCP for OpenClaw Looking for a Blazemeter MCP server for OpenClaw? ClawLink connects Blazemeter to OpenClaw and exposes 92 Blazemeter tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Blazemeter integration](https://claw-link.dev/hermes/blazemeter) works the same way. ## What the OpenClaw Blazemeter integration can do 92 Blazemeter tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 92. ### 30 of 92 Blazemeter tools for OpenClaw | Tool | What it does | |---|---| | **Convert transactions** `blazemeter_convert_transactions` | Convert transaction files to BlazeMeter DSL format for service virtualization | | **Create search** `blazemeter_create_search` | Execute a search query against BlazeMeter entities using advanced filtering and sorting | | **Export package** `blazemeter_export_package` | Export a package from BlazeMeter Asset Repository as a zip file | | **Export workspaces packages** `blazemeter_export_workspaces_packages` | Export multiple packages from a workspace as a zip file | | **Generate workspaces datamodels** `blazemeter_generate_workspaces_datamodels` | Generate test data from a data model in Asset Repository | | **Generate workspaces testdata** `blazemeter_generate_workspaces_testdata` | Generate synthetic test data on-the-fly without storing in Asset Repository | | **Get accounts** `blazemeter_get_accounts` | Retrieve a list of accounts associated with the authenticated user | | **Get API monitoring schedule** `blazemeter_get_api_monitoring_schedule` | Retrieve details of a specific API monitoring schedule by its ID | | **Get API monitoring schedules** `blazemeter_get_api_monitoring_schedules` | Retrieves a paginated list of API monitoring test schedules | | **Get generator functions** `blazemeter_get_generator_functions` | Retrieve all available test data generator functions from BlazeMeter Test Data API | | **Get generator seedlists** `blazemeter_get_generator_seedlists` | Retrieve a list of all available seed lists from BlazeMeter Test Data Management API | | **Get info health** `blazemeter_get_info_health` | Retrieve the BlazeMeter service health status | | **Get info version** `blazemeter_get_info_version` | Retrieve BlazeMeter service version information | | **Get masters reports main summary** `blazemeter_get_masters_reports_main_summary` | Retrieve request statistics summary for a master test run | | **Get multi test** `blazemeter_get_multi_test` | Retrieve details of a specific multi-test | | **Get multi tests** `blazemeter_get_multi_tests` | Retrieves a paginated list of multi-tests within a BlazeMeter workspace | | **Get private locations** `blazemeter_get_private_locations` | Retrieve a list of private locations filtered by account or workspace | | **Get project details** `blazemeter_get_project_details` | Retrieve detailed information about a specific project by its ID | | **Get projects** `blazemeter_get_projects` | Retrieve a list of projects within a specified workspace | | **Get regions** `blazemeter_get_regions` | Retrieve a list of all available test regions for API monitoring | | **Get search metadata** `blazemeter_get_search_metadata` | Retrieve metadata about searchable entities, fields, relationships, and operators in | | **Get shared folders** `blazemeter_get_shared_folders` | Retrieve a list of shared folders within a specified workspace | | **Get tags** `blazemeter_get_tags` | Retrieve a list of all tags from BlazeMeter Mock Services API | | **Get test details** `blazemeter_get_test_details` | Retrieve complete details of a specific test by its ID | | **Get test validations** `blazemeter_get_test_validations` | Retrieve validation results for a specific test by its ID | | **Get tests** `blazemeter_get_tests` | Retrieve a list of performance tests filtered by workspace or project | | **Get tests files** `blazemeter_get_tests_files` | List all files associated with a test | | **Get user** `blazemeter_get_user` | Retrieve the authenticated user's profile information including their default project and | | **Get user active sessions** `blazemeter_get_user_active_sessions` | Retrieve the list of active test sessions for the authenticated user | | **Get user invites** `blazemeter_get_user_invites` | Retrieve pending invites for the authenticated user | ## Example prompts **Convert Transactions** > Use Blazemeter to convert transactions and walk me through the result in plain English. **Create Search** > Search Blazemeter for what I need, summarize the results, and tell me the next best action. **Export Package** > Use Blazemeter to export package and walk me through the result in plain English. **Export Workspaces Packages** > Use Blazemeter to export workspaces packages and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Blazemeter working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right Blazemeter credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link Blazemeter without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Blazemeter. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Blazemeter actions to the runtime in a format your agent can reliably use. | 92 tools for Blazemeter are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Blazemeter to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Blazemeter in the browser, and the 92 tools above work from chat. There is no SDK and no config file, and the Blazemeter key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Blazemeter skill but can't call the tools The ClawHub skill teaches OpenClaw about Blazemeter, but the calls run through the ClawLink plugin and your connected account. Make sure Blazemeter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Blazemeter from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Blazemeter tools Blazemeter tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Blazemeter call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Blazemeter returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for Blazemeter. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw Blazemeter integration? Yes. ClawLink is the fastest way to connect OpenClaw to Blazemeter: link your Blazemeter account once in the browser and OpenClaw can call the Blazemeter API through 92 ready-made tools — no custom code or token handling. ### How do I add Blazemeter to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Blazemeter skill from ClawHub, then you click Connect in the dashboard to authorize Blazemeter. OpenClaw calls the tools from the next message — no config files, and the Blazemeter key you paste is stored server-side instead of in your environment. ### How long does it take to connect Blazemeter to OpenClaw? About two minutes. Sign in, click Connect next to Blazemeter in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Blazemeter up myself? The alternative to ClawLink is usually manual credential setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Blazemeter working from chat. ### OpenClaw installed the Blazemeter skill but can't call the tools The ClawHub skill teaches OpenClaw about Blazemeter, but the calls run through the ClawLink plugin and your connected account. Make sure Blazemeter is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.