Connect / OpenClaw

Connect

Connect Dexi to OpenClaw

MCP server · https://mcp.dexi.net/mcp

OpenClaw is the open-source personal AI agent that runs on your own machine or VPS and talks to you over Telegram, Discord, WhatsApp, Slack, iMessage, or the terminal. It speaks MCP natively and has a plugin system with an exclusive memory slot. Dexi connects either way — as a remote MCP server with OAuth (no API key), or as the memory plugin that makes your notes the agent’s long-term memory.

For an always-on agent, a hosted notes library is the natural second brain: everything you clip with the web clipper, forward to save@my.dexi.net, or pull in from RSS is there for OpenClaw to search, and whatever OpenClaw saves shows up in the Dexi app. This page is the setup reference; the why-and-what of the memory plugin lives at dexi.net/openclaw.

Listing: OpenClaw MCP documentation

What you need

  1. OpenClaw 2026.5.7 or newer (Node 22+) — openclaw --version.
  2. A Dexi account — free at app.dexi.net.

Setup

Add Dexi as an MCP server

Two commands: register the server (streamable HTTP + OAuth), then sign in once. Tools appear as dexi__search_notes, dexi__create_note, and so on.

openclaw mcp add dexi --url https://mcp.dexi.net/mcp --transport streamable-http --auth oauth
openclaw mcp login dexi
openclaw mcp probe dexi
  1. openclaw mcp add dexi --url https://mcp.dexi.net/mcp --transport streamable-http --auth oauth saves the server to ~/.openclaw/openclaw.json.
  2. openclaw mcp login dexi prints an authorize URL. Open it, sign in to Dexi, and approve — on the consent page you can restrict this connection to a single folder or tag. On a headless server, approve from any browser and finish with openclaw mcp login dexi --code <code> (the code is in the redirect URL).
  3. openclaw mcp probe dexi should report 12 tools. Restart the gateway (openclaw gateway restart) and ask: “search my Dexi notes for …”.

Or: Dexi as OpenClaw’s memory plugin

The openclaw-dexi plugin goes further than tools: it recalls relevant notes before every turn (injected as <dexi-context>), adds /remember and /recall, ships dexi-capture / dexi-recall / dexi-review skills, and can write one digest note per conversation (opt-in). It takes OpenClaw’s single memory slot (replacing the built-in memory-core), so pick this instead of the MCP-server entry if Dexi is your memory:

openclaw plugins install openclaw-dexi
openclaw plugins enable openclaw-dexi   # claims the memory slot
openclaw dexi setup                     # permissions + allowlist, then sign in
openclaw gateway restart
  1. openclaw plugins install openclaw-dexi, openclaw plugins enable openclaw-dexi (claims the memory slot from the built-in memory-core), then openclaw dexi setup — it grants the hook permissions, allowlists the dexi_* tools, and runs the same one-time OAuth sign-in (browser or paste-back). Add --read-only to request notes:read only, --session-digest to turn on the per-session digest note.
  2. openclaw gateway restart, then openclaw dexi status shows the config and a live probe; openclaw status lists Memory as enabled (plugin openclaw-dexi). Tools are dexi_search, dexi_get, dexi_list, dexi_save, dexi_append, dexi_tags, dexi_folders, and the review pair.

Try it

As an MCP server, Dexi’s tools appear in OpenClaw as dexi__search_notes, dexi__create_note, and so on (as the memory plugin: dexi_search, dexi_save, …). Try: “Search my Dexi notes for everything I’ve saved about vector databases and give me a briefing.” With the plugin, type /remember Railway healthchecks probe PORT, not the domain target port #infra to save a note without the model, or schedule an OpenClaw cron job that runs the dexi-review skill and quizzes you over Telegram.

Troubleshooting

The authorize URL expired before I approved

Dexi’s approval request is valid for ten minutes. Run openclaw mcp login dexi (or openclaw dexi login) again and complete the approval promptly.

OpenClaw is on a VPS and the browser callback can’t reach it

Use the paste-back flow: open the URL on your own machine, approve, then run openclaw mcp login dexi --code <code> (MCP server) or paste the final redirect URL into the terminal / run openclaw dexi login --code <value> (plugin). SSH port-forwarding the callback port also works. Tokens are stored under ~/.openclaw, so this is a one-time step.

Tools are there but the agent doesn’t use them

Name the source: “search my Dexi notes for…”. MCP tools carry the server prefix (dexi__*); the plugin’s are dexi_* and come with a memory prompt section that tells the model when to search. If both are present you’ll see duplicates — keep one (openclaw mcp unset dexi).

I want OpenClaw’s built-in memory back

openclaw config set plugins.slots.memory memory-core and restart the gateway. The Dexi plugin can stay installed; the MCP-server route keeps working alongside memory-core.

Disconnecting

In the Dexi app, open Settings → Connected apps to see every app connected to your account and disconnect any of them instantly. Revoking access there signs OpenClaw out of your notes no matter what’s configured on the client side.

Frequently asked questions

MCP server or memory plugin — which should I pick?

Both talk to the same Dexi account with the same kind of OAuth grant. The MCP-server entry works alongside OpenClaw’s built-in memory and exposes all twelve Dexi tools. The plugin takes the exclusive memory slot and adds what a plain server can’t: auto-recall before each turn, a memory prompt section, /remember and /recall, skills, and the optional session digest. Don’t configure both — you’d get duplicate tools.

What does the memory plugin send to Dexi?

Only what its features need: the current message (channel metadata stripped) as a search query for auto-recall, the arguments of tools the model calls, and — only if you turn on the session digest — a distilled note of the conversation’s questions and last answer. Never full transcripts or OpenClaw’s local memory files. Set readOnly: true and it can’t write at all.

Does OpenClaw need a Dexi API key?

No. OpenClaw (or the plugin) registers itself as an OAuth client and you approve it once on Dexi’s sign-in page. Revoke it any time from Settings → Connected apps in Dexi; openclaw mcp logout dexi or openclaw dexi logout clears the token on the OpenClaw side.

Which LLM does Dexi work with in OpenClaw?

Any of them. OpenClaw is model-agnostic and Dexi’s MCP server doesn’t care which model is driving — the tools behave the same with every provider OpenClaw supports, local Ollama models included.

Can I limit what OpenClaw can see?

Yes. On the consent page, restrict the connection to one folder or one tag (or both). OpenClaw then reads and writes only inside that boundary; you can change or revoke it later from Settings → Connected apps.

Other clients

Dexi works with any MCP client that supports streamable HTTP with OAuth — see the overview, or jump to a guide: Claude, Claude Code, ChatGPT, Goose, Hermes Agent, Cursor, VS Code, Smithery.

Questions?

Email team@dexi.net — see also Support and our Privacy Policy.