OpenClaw puts an always-available assistant in WhatsApp, Telegram, Slack, Discord, and other channels. Add Pathbound as a remote MCP server and it can read the contact, company, timeline, conversations, and recent activity behind the name in the message.
OpenClaw is built to receive work from the channels you already use. Pathbound supplies the customer record underneath that work, with identities resolved across the sources you have connected.
Check an account before a call, read the history behind a support question, or look up recent activity without opening each source yourself.
Pathbound matches CRM records, support history, email, meetings, and website events to the same contact and company before OpenClaw requests them.
API key scopes enforce what the agent can read. OpenClaw’s per-server tool filter keeps write tools out of the first tool catalog as a second boundary.
This path uses OpenClaw’s built-in outbound MCP registry. You do not need a Pathbound or OpenClaw plugin.
In Pathbound, open REST API keys and create a key with contacts:read, companies:read, and events:read. Leave write and action scopes off.
Add the following line to ~/.openclaw/.env. OpenClaw loads this global file when a Gateway managed by launchd or systemd starts.
PATHBOUND_API_KEY=sk_your_api_keyRegister the endpoint with Streamable HTTP transport. The tool filter removes common write-tool names from the catalog; the read-only key remains the enforcement layer.
openclaw mcp set pathbound \
'{"url":"https://mcp.pathbound.ai/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${PATHBOUND_API_KEY}"},"toolFilter":{"exclude":["create_*","update_*","delete_*","gmail_send_email","resend_*"]}}'The live probe should connect and report the Pathbound tools. Restart the Gateway so new messaging sessions receive the updated tool catalog.
openclaw mcp doctor pathbound --probe
openclaw gateway restartOpenClaw also exposes this registry in its Control UI under MCP. See the OpenClaw MCP reference for transport, filtering, and diagnostics.
Send one of these questions from an allowed OpenClaw channel. Confirm that the answer names the Pathbound record and matches what you see in the dashboard before relying on it in a recurring task.
Find Acme in Pathbound. Summarize the company, its contacts, and everything that happened in the last seven days. Include the source and date for each event.
Read the Pathbound profile and conversation history for [email protected]. What was the last question she asked, and what did our team promise next?
Which contacts visited the pricing page this week? Use Pathbound’s server-side aggregation or filters. Do not update any records.
For a repeatable workflow, use the tested trial-signup research recipe as the starting instruction.
OpenClaw can receive instructions through real messaging accounts. Treat channel access and customer-data access as separate controls.
Use the smallest API key scope that serves the job. Revoke or rotate the key from the Pathbound dashboard. Keys without actions:write do not receive action tools.
Restrict who can message the agent, keep group behavior explicit, and review the active tool profile. OpenClaw’s security guide covers channel allowlists, file permissions, and Gateway exposure.
Yes. OpenClaw can consume remote Streamable HTTP MCP servers. Add https://mcp.pathbound.ai/mcp to OpenClaw’s MCP registry, authenticate with a scoped Pathbound API key, and verify the live tool catalog with openclaw mcp doctor pathbound --probe.
No. OpenClaw already has an outbound MCP client, and Pathbound already exposes its tools over MCP. A plugin would package setup or instructions; it is not required for the connection.
A scoped API key is predictable for a long-running OpenClaw Gateway and can be limited to read-only contact, company, and event access. Store it in OpenClaw’s global runtime environment, not in a project repository.
Only when the Pathbound key includes the required write scopes and the connected source allows the tool. Start read-only. If you later allow writes, review OpenClaw’s channel access and tool policy first. Versioning and rollback are not live yet.
The configured OpenClaw agent can use Pathbound from its eligible messaging sessions, subject to OpenClaw’s tool profile and channel policy. That can include WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Microsoft Teams, and WebChat.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.