How to connect Supermemory to OpenClaw
Connect Supermemory to OpenClaw with ClawLink: paste your Supermemory key once and 86 tools work from chat. No MCP server to run, nothing stored on your machine.

Supermemory is a memory and context API for ingesting, organizing, searching, and recalling information across applications.. Once connected, OpenClaw can read and act on Supermemory from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Supermemory 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 Supermemory setup: install one ClawHub skill, connect Supermemory in the browser, and OpenClaw can call real Supermemory 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 Supermemory.
- 1
Install 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 Supermemory
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Supermemory?"
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 Supermemory in the ClawLink dashboard — paste your Supermemory API key once.
Verify the connection by asking OpenClaw:
Use Supermemory to count namespace document memories 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 Supermemory is connected in the dashboard, that agent calls the same 86 Supermemory tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Supermemory MCP for OpenClaw
Looking for a Supermemory MCP server for OpenClaw? ClawLink connects Supermemory to OpenClaw and exposes 86 Supermemory tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Supermemory integration works the same way.
What the OpenClaw Supermemory integration can do
86 Supermemory tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 86.
30 of 86 Supermemory tools for OpenClaw
| Tool | What it does |
|---|---|
Count namespace document memories supermemory_count_namespace_document_memories | Count live memories in a namespace for up to 100 public document IDs |
Get account status supermemory_get_account_status | Return the connected Supermemory organization's plan, credit balance, high-level usage, and |
Get automatic topups supermemory_get_automatic_topups | Deprecated legacy v3 API, scheduled to shut down December 31, 2026 |
Get billing usage supermemory_get_billing_usage | Deprecated legacy v3 API; provider shutdown is December 31, 2026 |
Get billing usage events supermemory_get_billing_usage_events | Deprecated legacy v3 API, scheduled to shut down December 31, 2026 |
Get connection supermemory_get_connection | Deprecated by the provider: this legacy v3 endpoint shuts down December 31, 2026 |
Get connector supermemory_get_connector | Read a connector in a namespace, including its setup, selection, and latest sync status |
Get container tag supermemory_get_container_tag | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
Get container tag merge supermemory_get_container_tag_merge | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
Get document supermemory_get_document | Get one document's content, metadata, source details, and processing status by document ID |
Get document chunks supermemory_get_document_chunks | Return the ordered extracted chunks for one processed document |
Get document file URL supermemory_get_document_file_url | Deprecated by the provider: this legacy endpoint shuts down December 31, 2026 |
Get error analytics supermemory_get_error_analytics | Deprecated legacy v3 endpoint scheduled to shut down December 31, 2026 |
Get namespace supermemory_get_namespace | Read a namespace's supporting context and lifecycle timestamps |
Get namespace document supermemory_get_namespace_document | Retrieve a document's canonical content, metadata, and processing state by document ID or |
Get namespace memory supermemory_get_namespace_memory | Retrieve one memory by ID within a namespace, including its text, metadata, version, and recall |
Get namespace profile supermemory_get_namespace_profile | Read the continuously maintained profile of a namespace's subject without a search query |
Get namespace profile buckets supermemory_get_namespace_profile_buckets | Inspect the profile taxonomy active in a Supermemory namespace |
Get organization supermemory_get_organization | Read the connected organization's shared background that guides memory formation across all |
Get profile supermemory_get_profile | Retrieve the static, dynamic, or bucketed profile learned for one container tag, optionally |
Get profile buckets supermemory_get_profile_buckets | Deprecated by the provider: this legacy v4 endpoint shuts down on December 31, 2026 |
Get provider connection supermemory_get_provider_connection | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
Get settings supermemory_get_settings | Deprecated legacy v3 API, scheduled to shut down December 31, 2026 |
Get usage analytics supermemory_get_usage_analytics | Deprecated legacy v3 API, scheduled to shut down December 31, 2026 |
List all connectors supermemory_list_all_connectors | List one page of connectors across every namespace the API key can read, optionally filtered by |
List connection documents supermemory_list_connection_documents | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
List connection resources supermemory_list_connection_resources | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
List connections supermemory_list_connections | Deprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026 |
List connectors supermemory_list_connectors | List one page of connectors that sync into a namespace, optionally filtered by provider |
List container tags supermemory_list_container_tags | Deprecated by the provider: the legacy v3 API shuts down December 31, 2026 |
Try it: find the Supermemory tool you need
Browse the 30 Supermemory tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Supermemory to count namespace document memories 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 Supermemory working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Supermemory API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Supermemory 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 Supermemory. | 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 Supermemory actions to the runtime in a format your agent can reliably use. | 86 tools for Supermemory are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Supermemory 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 Supermemory in the browser, and the 86 tools above work from chat. There is no SDK and no config file, and the Supermemory 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 Supermemory skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supermemory, but the calls run through the ClawLink plugin and your connected account. Make sure Supermemory 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 Supermemory 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 Supermemory tools
Supermemory 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 Supermemory 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.
Supermemory 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 Supermemory 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 Supermemory integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Supermemory: link your Supermemory account once in the browser and OpenClaw can call the Supermemory API through 86 ready-made tools — no custom code or token handling.
How do I add Supermemory to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Supermemory skill from ClawHub, then you click Connect in the dashboard to authorize Supermemory. OpenClaw calls the tools from the next message — no config files, and the Supermemory key you paste is stored server-side instead of in your environment.
How long does it take to connect Supermemory to OpenClaw?
About two minutes. Sign in, click Connect next to Supermemory in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Supermemory 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 Supermemory working from chat.
OpenClaw installed the Supermemory skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supermemory, but the calls run through the ClawLink plugin and your connected account. Make sure Supermemory 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
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
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.