# How to connect MailerCheck to OpenClaw (paste one key, 9 tools) > Connect MailerCheck to OpenClaw with ClawLink: paste your MailerCheck key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/mailercheck The usual route to MailerCheck 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 MailerCheck setup: install one ClawHub skill, connect MailerCheck in the browser, and OpenClaw can call real MailerCheck 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 MailerCheck. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect MailerCheck** — 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 mailercheck # connect MailerCheck (browser OAuth) npx -y @useclawlink/cli actions mailercheck # list available actions npx -y @useclawlink/cli run mailercheck --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 MailerCheck in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your MailerCheck API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from MailerCheck, summarize it in plain English, and point out anything that needs attention. ### 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 MailerCheck is connected in the dashboard, that agent calls the same 9 MailerCheck 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). ## MailerCheck MCP for OpenClaw Looking for a MailerCheck MCP server for OpenClaw? ClawLink connects MailerCheck to OpenClaw and exposes 9 MailerCheck 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 MailerCheck integration](https://claw-link.dev/hermes/mailercheck) works the same way. ## What the OpenClaw MailerCheck integration can do 9 MailerCheck tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9. ### 8 of 9 MailerCheck tools for OpenClaw | Tool | What it does | |---|---| | **Get credit balance** `mailercheck_get_credit_balance` | Return the current MailerCheck verification-credit balance | | **Get current account** `mailercheck_get_current_account` | Return the connected MailerCheck user and account identity | | **Get verification list** `mailercheck_get_verification_list` | Return one verification list, including its status, item count, verification timing, and | | **List verification lists** `mailercheck_list_verification_lists` | Return one page of verification lists for the connected MailerCheck account, with an opaque | | **List verification results** `mailercheck_list_verification_results` | Return one page of email-level results for a verification list, optionally filtered by | | **Create verification list** `mailercheck_create_verification_list` | Create a MailerCheck verification list by ingesting a name and email-address array | | **Start list verification** `mailercheck_start_list_verification` | Irreversibly start verification of every address in a MailerCheck list | | **Verify email** `mailercheck_verify_email` | Consumes exactly one MailerCheck verification credit on every successful call | ## Example prompts **Get Credit Balance** > Pull the relevant data from MailerCheck, summarize it in plain English, and point out anything that needs attention. **Get Current Account** > Pull the relevant data from MailerCheck, summarize it in plain English, and point out anything that needs attention. **Get Verification List** > Pull the relevant data from MailerCheck, summarize it in plain English, and point out anything that needs attention. **List Verification Lists** > List the relevant items in MailerCheck, group them by priority, and recommend what OpenClaw should do next. ## 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 MailerCheck working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the MailerCheck API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected MailerCheck 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 MailerCheck. | 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 MailerCheck actions to the runtime in a format your agent can reliably use. | 9 tools for MailerCheck are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes MailerCheck 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 MailerCheck in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the MailerCheck 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 MailerCheck skill but can't call the tools The ClawHub skill teaches OpenClaw about MailerCheck, but the calls run through the ClawLink plugin and your connected account. Make sure MailerCheck 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 MailerCheck 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 MailerCheck tools MailerCheck 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 MailerCheck 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. ### MailerCheck 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 MailerCheck has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw MailerCheck integration? Yes. ClawLink is the fastest way to connect OpenClaw to MailerCheck: link your MailerCheck account once in the browser and OpenClaw can call the MailerCheck API through 9 ready-made tools — no custom code or token handling. ### How do I add MailerCheck to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink MailerCheck skill from ClawHub, then you click Connect in the dashboard to authorize MailerCheck. OpenClaw calls the tools from the next message — no config files, and the MailerCheck key you paste is stored server-side instead of in your environment. ### How long does it take to connect MailerCheck to OpenClaw? About two minutes. Sign in, click Connect next to MailerCheck in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring MailerCheck 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 MailerCheck working from chat. ### OpenClaw installed the MailerCheck skill but can't call the tools The ClawHub skill teaches OpenClaw about MailerCheck, but the calls run through the ClawLink plugin and your connected account. Make sure MailerCheck 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 ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Connect Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences