Supermemory + OpenClaw
Connect Supermemory to OpenClaw
Prepare a grounded source-backed memory briefing
Read documents with OpenClaw and Agent200. Prepare a source-backed memory briefing within the configured Supermemory account scope.
On this page
Overview
Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one document the user can access. A saved setting alone does not verify the read.
Start with one identified document. Preserve returned document content, source and container tags; report missing data and keep the workflow read-only.
Provider reference: Supermemory API.
Use the provider credential described on the Supermemory parent page. Keep it in secure configuration and verify the selected tenant or account before reading.
- Connector
- Supermemory
- Works with
- OpenClaw · Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 4 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Supermemory enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Supermemory to OpenClaw
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Configure Supermemory access
Use the provider-issued credential through the supported Agent200 connection route. Confirm the account scope and inspect the advertised tools before reading.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Supermemory document I identify and prepare a source-backed memory briefing. Name the source and use only document content, source and container tags. State access gaps; do not change records.
What should come back
- The selected document is identified.
- Only the returned document content, source and container tags are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected document ID, account scope, read permission and pagination. A semantic match is not proof of complete recall. Name returned sources and container scope, and allow for indexing or processing lag.
Get your API key
Create a key in the Agent200 dashboard. It reaches Supermemory and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Supermemory to OpenClaw.
Goal: connect Supermemory to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/supermemory/framework/openclaw/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Supermemory is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands. 4. Check it works with this request: "Read the Supermemory document I identify and prepare a source-backed memory briefing. Name the source and use only document content, source and container tags. State access gaps; do not change records." What should come back: - The selected document is identified. - Only the returned document content, source and container tags are reported. - Access gaps and missing context are explicit; no source data is changed. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/supermemory/framework/openclaw.md
Supermemory tools OpenClaw can call
-
Search documents
Readsupermemory_search_documentsSearch indexed documents within a specified container.
-
Read a document
Readsupermemory_get_documentRetrieve one identified document when available.
-
List documents
Readsupermemory_list_documentsFind indexed documents in the key’s scope.
-
Search memories
Readsupermemory_search_memoriesSearch generated memories with source references.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in Supermemory.
-
02
OpenClaw picks a tool
It sees the Supermemory tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Supermemory with your Agent200 API key, within the endpoints your project allows.
-
04
OpenClaw answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The source cannot be read
Check the selected document ID, account scope, read permission and pagination. A semantic match is not proof of complete recall. Name returned sources and container scope, and allow for indexing or processing lag.
FAQ
How do I verify this result?
Compare the named document and returned document content, source and container tags with the source. Treat missing information as missing, not as a fact.
