# How to connect MXToolbox to OpenClaw (paste one key, 13 tools) > Connect MXToolbox to OpenClaw with ClawLink: paste your MXToolbox key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/mx-toolbox The usual route to MXToolbox 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 MXToolbox setup: install one ClawHub skill, connect MXToolbox in the browser, and OpenClaw can call real MXToolbox 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 MXToolbox. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect MXToolbox** — 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 mx-toolbox # connect MXToolbox (browser OAuth) npx -y @useclawlink/cli actions mx-toolbox # list available actions npx -y @useclawlink/cli run mx-toolbox --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 MXToolbox in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your MXToolbox API key once. Verify the connection by asking OpenClaw: > Use MXToolbox to lookup bimi record 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 MXToolbox is connected in the dashboard, that agent calls the same 13 MXToolbox 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). ## MXToolbox MCP for OpenClaw Looking for a MXToolbox MCP server for OpenClaw? ClawLink connects MXToolbox to OpenClaw and exposes 13 MXToolbox 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 MXToolbox integration](https://claw-link.dev/hermes/mx-toolbox) works the same way. ## What the OpenClaw MXToolbox integration can do 13 MXToolbox tools are ready for OpenClaw once the account is connected. ### All 13 MXToolbox tools for OpenClaw | Tool | What it does | |---|---| | **Lookup bimi record** `mx_toolbox_lookup_bimi_record` | Retrieves BIMI (Brand Indicators for Message Identification) record and diagnostic information | | **Lookup blacklist** `mx_toolbox_lookup_blacklist` | Perform a blacklist check on a domain or IP | | **Lookup dkim** `mx_toolbox_lookup_dkim` | Retrieve DKIM (DomainKeys Identified Mail) records for a domain | | **Lookup dmarc** `mx_toolbox_lookup_dmarc` | Retrieves DMARC (Domain-based Message Authentication, Reporting & Conformance) records for a | | **Lookup dns** `mx_toolbox_lookup_dns` | Performs comprehensive DNS health check and retrieves name server records for a domain | | **Lookup http** `mx_toolbox_lookup_http` | Perform an HTTP test on a domain | | **Lookup mta sts record** `mx_toolbox_lookup_mta_sts_record` | Lookup MTA-STS record for a domain | | **Lookup mx** `mx_toolbox_lookup_mx` | Retrieves MX (Mail Exchange) records for a domain | | **Lookup ping** `mx_toolbox_lookup_ping` | Performs a ping test to check network connectivity and measure round-trip time to a domain or | | **Lookup smtp** `mx_toolbox_lookup_smtp` | Perform an SMTP connectivity test on a domain | | **Lookup spf** `mx_toolbox_lookup_spf` | Retrieve SPF records for a specified domain | | **Monitor status** `mx_toolbox_monitor_status` | Retrieves the current status of all monitors configured in the MX Toolbox account | | **Usage check** `mx_toolbox_usage_check` | Retrieve API usage statistics for DNS and network lookups | ## Example prompts **Lookup Bimi Record** > Use MXToolbox to lookup bimi record and walk me through the result in plain English. **Lookup Blacklist** > Use MXToolbox to lookup blacklist and walk me through the result in plain English. **Lookup Dkim** > Use MXToolbox to lookup dkim and walk me through the result in plain English. **Lookup Dmarc** > Use MXToolbox to lookup dmarc and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 MXToolbox working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the MXToolbox API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected MXToolbox account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for MXToolbox. | 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 MXToolbox actions to the runtime in a format your agent can reliably use. | 13 tools for MXToolbox are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes MXToolbox 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 MXToolbox in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the MXToolbox 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 MXToolbox skill but can't call the tools The ClawHub skill teaches OpenClaw about MXToolbox, but the calls run through the ClawLink plugin and your connected account. Make sure MXToolbox 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 MXToolbox 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 MXToolbox tools MXToolbox 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 MXToolbox 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. ### MXToolbox 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. ### API key setup works but results look incomplete Double-check that the API key for MXToolbox has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw MXToolbox integration? Yes. ClawLink is the fastest way to connect OpenClaw to MXToolbox: link your MXToolbox account once in the browser and OpenClaw can call the MXToolbox API through 13 ready-made tools — no custom code or token handling. ### How do I add MXToolbox to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink MXToolbox skill from ClawHub, then you click Connect in the dashboard to authorize MXToolbox. OpenClaw calls the tools from the next message — no config files, and the MXToolbox key you paste is stored server-side instead of in your environment. ### How long does it take to connect MXToolbox to OpenClaw? About two minutes. Sign in, click Connect next to MXToolbox in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring MXToolbox up myself? The alternative to ClawLink is usually manual API key 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 MXToolbox working from chat. ### OpenClaw installed the MXToolbox skill but can't call the tools The ClawHub skill teaches OpenClaw about MXToolbox, but the calls run through the ClawLink plugin and your connected account. Make sure MXToolbox 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.