Connect / Hermes Agent

Connect

Connect Dexi to Hermes Agent

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

Hermes Agent is Nous Research’s open-source, self-improving AI agent. It runs anywhere from a laptop terminal to a $5 VPS, talks to you over Telegram, Discord, Slack, WhatsApp, Signal, or email, and extends through MCP servers. Dexi connects as a remote MCP server with OAuth — no API key, no local files to sync.

For an agent that lives on a server, 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 Hermes to search, and whatever Hermes saves shows up in the Dexi app.

Listing: Hermes Agent MCP documentation

What you need

  1. Hermes Agent installed and set up (hermes setup), on any platform.
  2. A Dexi account — free at app.dexi.net.

Setup

Add Dexi to your Hermes config

Open ~/.hermes/config.yaml (or the profile’s config if you use profiles) and add Dexi under mcp_servers:

mcp_servers:
  dexi:
    url: "https://mcp.dexi.net/mcp"
    auth: oauth
  1. Save the file and start (or restart) Hermes. It discovers Dexi’s OAuth metadata, registers itself as a client, and on the first tool call prints an authorize URL — and opens your browser when it can.
  2. Sign in to Dexi and approve. On the consent page you can restrict this connection to a single folder or tag if you want Hermes to see only part of your library.
  3. Running Hermes on a headless server? Open the printed URL in any browser, approve, then paste the redirect URL back into the terminal when Hermes prompts (“Or paste the redirect URL here…”). To redo the sign-in later, run hermes mcp login dexi.

Or: Dexi as Hermes’ memory provider

The dexi memory-provider plugin goes further than tools: it recalls relevant notes before every turn (injected as <dexi-context>), adds dexi:capture / dexi:recall / dexi:review skills, and can write one digest note per session (opt-in). Hermes allows one external memory provider at a time, so pick this instead of the mcp_servers entry if Dexi is your memory:

hermes plugins install dexi/hermes-plugin --enable
hermes memory setup      # choose: dexi
hermes dexi login
  1. Run hermes memory setup and pick dexi (or set memory.provider: dexi in ~/.hermes/config.yaml), then hermes dexi login for the one-time OAuth approval — same browser or paste-back flow.
  2. hermes memory status confirms it’s active. Tools are dexi_search, dexi_get, dexi_list, dexi_save, dexi_append, dexi_tags, dexi_folders, and the review pair. Config lives in ~/.hermes/dexi.json (auto-recall on by default; session digest off; read_only available).

Try it

As an MCP server, Dexi’s tools appear in Hermes as mcp_dexi_search_notes, mcp_dexi_create_note, and so on (as the memory provider: dexi_search, dexi_save, …). Try: “Search my Dexi notes for everything I’ve saved about vector databases and give me a briefing.” Or schedule a daily cron that runs the review skill and quizzes you over Telegram.

Troubleshooting

The authorize URL expired before I approved

Dexi’s approval request is valid for ten minutes. Trigger another tool call (or run hermes mcp login dexi) to get a fresh URL and complete the approval promptly.

Hermes 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, and paste the final redirect URL (or just its ?code=…&state=… part) into the Hermes terminal. SSH port-forwarding the callback port also works. Tokens are cached in ~/.hermes/mcp-tokens/dexi.json, so this is a one-time step.

Tools are there but Hermes doesn’t use them

Name the source: “search my Dexi notes for…”. Hermes prefixes every MCP tool with the server name, so look for mcp_dexi_* in its tool list. If the server is missing, check the YAML indentation under mcp_servers and restart.

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 Hermes Agentout of your notes no matter what’s configured on the client side.

Frequently asked questions

MCP server or memory provider — which should I pick?

Both talk to the same Dexi account with the same OAuth grant. The MCP-server entry works alongside whichever memory provider you already use (built-in, Honcho, Mem0, …) and exposes all twelve Dexi tools. The dexi memory-provider plugin takes Hermes’ single external-provider slot and adds what a plain server can’t: auto-recall before each turn, skills, and the optional session digest. Don’t configure both — you’d get duplicate tools.

What does the memory provider send to Dexi?

Only what its features need: the current message 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 session’s questions and last answer. Never full transcripts or Hermes’ own MEMORY.md/USER.md. Set read_only: true and it can’t write at all.

Does Hermes need a Dexi API key?

No. Hermes 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; hermes mcp remove dexi clears the cached tokens on the Hermes side.

Which LLM does Dexi work with in Hermes?

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

Can I limit what Hermes can see?

Yes. On the consent page, restrict the connection to one folder or one tag (or both). Hermes 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, Cursor, VS Code, Smithery.

Questions?

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