How to connect Honcho to OpenClaw
Connect Honcho to OpenClaw with ClawLink: paste your Honcho key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.
HonchoAPI KEYMCPHoncho provides memory, context, and theory-of-mind infrastructure for building stateful AI agents.. Once connected, OpenClaw can read and act on Honcho from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Honcho 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 Honcho setup: install one ClawHub skill, connect Honcho in the browser, and OpenClaw can call real Honcho actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Honcho skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Honcho" (hith3sh/honcho-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/honcho-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Honcho.
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 Honcho
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Honcho?"
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 Honcho in the ClawLink dashboard — paste your Honcho API key once.
Verify the connection by asking OpenClaw:
Use Honcho to chat with peer 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 Honcho is connected in the dashboard, that agent calls the same 16 Honcho tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Honcho MCP for OpenClaw
Looking for a Honcho MCP server for OpenClaw? ClawLink connects Honcho to OpenClaw and exposes 16 Honcho tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Honcho integration works the same way.
What the OpenClaw Honcho integration can do
16 Honcho tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16.
15 of 16 Honcho tools for OpenClaw
| Tool | What it does |
|---|---|
Chat with peer honcho_chat_with_peer | Run usage-bearing agentic search and reasoning over a peer's learned representation to answer a |
Get message honcho_get_message | Return one message by its exact ID within a session |
Get peer representation honcho_get_peer_representation | Return a curated subset of conclusions representing a peer |
List conclusions honcho_list_conclusions | Return one page of stored conclusions in a workspace; use Search Conclusions for semantic |
List messages honcho_list_messages | Return one page of messages in a session; use Get Message for exact-ID retrieval |
List peers honcho_list_peers | Return one page of peers in a workspace |
List sessions honcho_list_sessions | Return one page of sessions in a workspace |
List workspaces honcho_list_workspaces | Return one page of Honcho workspaces visible to the connected admin key |
Search conclusions honcho_search_conclusions | Semantically search stored conclusions in a workspace |
Search messages honcho_search_messages | Semantically search messages at workspace, peer, or session scope |
Create conclusions honcho_create_conclusions | Store a batch of 1-100 explicit conclusions about peers, optionally tied to sessions |
Create messages honcho_create_messages | Add a batch of 1-100 attributed messages to a Honcho session |
Get or create peer honcho_get_or_create_peer | Return a peer by ID within a workspace, creating it with the supplied metadata and |
Get or create session honcho_get_or_create_session | Return a session by ID, or create it with initial peers, metadata, and configuration when absent |
Get or create workspace honcho_get_or_create_workspace | Return a workspace by ID, or create it with metadata and configuration when absent |
Try it: find the Honcho tool you need
Browse the 15 Honcho tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Honcho to chat with peer and walk me through the result in plain English.
Pull the relevant data from Honcho, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Honcho, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Honcho, 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 Honcho working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Honcho API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Honcho 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 Honcho. | 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 Honcho actions to the runtime in a format your agent can reliably use. | 16 tools for Honcho are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Honcho 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 Honcho in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Honcho 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 Honcho skill but can't call the tools
The ClawHub skill teaches OpenClaw about Honcho, but the calls run through the ClawLink plugin and your connected account. Make sure Honcho 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 Honcho 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 Honcho tools
Honcho 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 Honcho 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.
Honcho 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 Honcho 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 Honcho integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Honcho: link your Honcho account once in the browser and OpenClaw can call the Honcho API through 16 ready-made tools — no custom code or token handling.
How do I add Honcho to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Honcho skill from ClawHub, then you click Connect in the dashboard to authorize Honcho. OpenClaw calls the tools from the next message — no config files, and the Honcho key you paste is stored server-side instead of in your environment.
How long does it take to connect Honcho to OpenClaw?
About two minutes. Sign in, click Connect next to Honcho in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Honcho 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 Honcho working from chat.
OpenClaw installed the Honcho skill but can't call the tools
The ClawHub skill teaches OpenClaw about Honcho, but the calls run through the ClawLink plugin and your connected account. Make sure Honcho 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
DataRobot tools
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Connect Chatbotkit
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.