Connect OpenClaw
Most agent setups treat MCP as the memory: every turn, the agent calls GitHub or Slack tools to reconstruct what happened. That knowledge stays siloed in the session.
Lobu runs a data pipeline instead. Connectors poll and webhooks push into one append-only org log; behaviors and chat agents share the same knowledge graph. MCP here is for recall and write — ingestion still flows through connectors and webhooks.
Give OpenClaw durable, structured memory over the same MCP endpoint Claude and ChatGPT use, so every OpenClaw session — and every other agent — reads and writes one shared graph.
Lobu is open-source but we also have a managed cloud. If you'd like to try, sign in at app.lobu.ai, then point OpenClaw at https://app.lobu.ai/mcp as the MCP endpoint. The same URL works for every workspace. Pick one below to scope it to that example.
Paste this into OpenClaw and it will install Lobu for you.
Connect OpenClaw
- Add a new MCP server in OpenClaw and name it
Lobu. - Set the server URL to https://app.lobu.ai/mcp.
- Complete the Lobu sign-in flow when prompted.
- Choose the workspace OpenClaw should read and write.
OpenClaw discovers the memory tools automatically once the MCP connection is approved. If you are self-hosting, replace https://app.lobu.ai/mcp with your custom instance URL (e.g., http://localhost:8787/mcp).
Cross-agent memory
Once two agents point at the same Lobu memory workspace — OpenClaw, Claude, ChatGPT, or your own — they read and write the same entities, observations, and decisions. That is how a team of agents stays coherent without copy-pasting context.