How to connect Bouncer to OpenClaw
Connect Bouncer to OpenClaw with ClawLink: paste your Bouncer key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
BouncerAPI KEYMCPBouncer is an email verification and validation service that helps ensure email deliverability by verifying email addresses through real-time and batch processing APIs.. Once connected, OpenClaw can read and act on Bouncer from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Bouncer 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 Bouncer setup: install one ClawHub skill, connect Bouncer in the browser, and OpenClaw can call real Bouncer 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 Bouncer.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Bouncer
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Bouncer?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Bouncer in the ClawLink dashboard — paste your Bouncer API key once.
Verify the connection by asking OpenClaw:
Use Bouncer to check toxicity list job status 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Bouncer is connected in the dashboard, that agent calls the same 10 Bouncer tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Bouncer MCP for OpenClaw
Looking for a Bouncer MCP server for OpenClaw? ClawLink connects Bouncer to OpenClaw and exposes 10 Bouncer tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Bouncer integration works the same way.
What the OpenClaw Bouncer integration can do
10 Bouncer 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 10.
8 of 10 Bouncer tools for OpenClaw
| Tool | What it does |
|---|---|
Check toxicity list job status bouncer_check_toxicity_list_job_status | Check the status of a specific toxicity list job |
Get batch results bouncer_get_batch_results | Retrieve the results of a batch verification process |
Get credits bouncer_get_credits | Retrieve the current credit balance for the account |
Verify domain bouncer_verify_domain | Verify the validity and configuration of a domain |
Verify email bouncer_verify_email | Verify a single email address in real-time |
Create batch request bouncer_create_batch_request | Initiates an asynchronous batch email verification request |
Create toxicity list job bouncer_create_toxicity_list_job | Create a toxicity analysis job for a list of email addresses |
Finish batch bouncer_finish_batch | Mark a batch verification process as finished early |
Try it: find the Bouncer tool you need
Browse the 8 Bouncer tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Bouncer to check toxicity list job status and walk me through the result in plain English.
Pull the relevant data from Bouncer, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Bouncer, summarize it in plain English, and point out anything that needs attention.
Use Bouncer to verify domain 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 Bouncer working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Bouncer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bouncer 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 Bouncer. | 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 Bouncer actions to the runtime in a format your agent can reliably use. | 10 tools for Bouncer are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Bouncer 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 Bouncer in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Bouncer key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Bouncer skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bouncer, but the calls run through the ClawLink plugin and your connected account. Make sure Bouncer 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 Bouncer 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 Bouncer tools
Bouncer 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 Bouncer 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.
Bouncer 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 Bouncer has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Bouncer integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Bouncer: link your Bouncer account once in the browser and OpenClaw can call the Bouncer API through 10 ready-made tools — no custom code or token handling.
How do I add Bouncer to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bouncer skill from ClawHub, then you click Connect in the dashboard to authorize Bouncer. OpenClaw calls the tools from the next message — no config files, and the Bouncer key you paste is stored server-side instead of in your environment.
How long does it take to connect Bouncer to OpenClaw?
About two minutes. Sign in, click Connect next to Bouncer in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Bouncer 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 Bouncer working from chat.
OpenClaw installed the Bouncer skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bouncer, but the calls run through the ClawLink plugin and your connected account. Make sure Bouncer 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.
