How to connect Zep to Hermes Agent (paste one key, 41 tools)

Most guides for giving Hermes Agent Zep access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Zep setup: pair once in the browser and your always-on Hermes agent can act on Zep for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Zep.

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Zep
Paste your API key in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Zep?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Zep in the ClawLink dashboard — paste your Zep API key once.

Verify the connection by asking Hermes:

Pull the relevant data from Zep, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The Hermes 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 login

login opens the same browser approval and stores a credential locally. Once Zep is connected in the dashboard, that agent calls the same 41 Zep tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Zep MCP for Hermes

Looking for a Zep MCP server for Hermes Agent? ClawLink connects Zep to Hermes Agent and exposes 41 Zep tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Zep integration works the same way.

What the Hermes Agent Zep integration can do

41 Zep tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 41.

30 of 41 Zep tools for Hermes

Tool	What it does
Get edge `zep_get_edge`	Retrieve a specific edge by its UUID from the Zep knowledge graph
Get graph by ID `zep_get_graph_by_id`	Retrieve a graph by its unique identifier from Zep
Get group `zep_get_group`	Retrieve a group by ID from Zep
Get node edges `zep_get_node_edges`	Retrieve all entity edges for a specific node in the Zep knowledge graph
Get project info `zep_get_project_info`	Retrieve project information based on the provided API key
Get session `zep_get_session`	Retrieve a session by its unique identifier from Zep
Get session memory `zep_get_session_memory`	Retrieve memory for a given session including relevant facts and entities
Get session message `zep_get_session_message`	Retrieve a specific message by UUID from a Zep session
Get session messages `zep_get_session_messages`	Retrieve messages for a given session from Zep
Get task status `zep_get_task_status`	Check the status of asynchronous operations in Zep
Get thread messages `zep_get_thread_messages`	Retrieve conversation history for a specific thread from Zep
Get thread user context `zep_get_thread_user_context`	Retrieve the most relevant user context from the user graph based on thread messages
Get user `zep_get_user`	Retrieve a user by their user ID from Zep
Get user node `zep_get_user_node`	Retrieve a user's graph node and summary from Zep
Get user nodes `zep_get_user_nodes`	Retrieve all nodes for a specific user from their graph in Zep
Get user sessions `zep_get_user_sessions`	Retrieve all sessions for a user from Zep
Get user threads `zep_get_user_threads`	Retrieve all threads for a specific user from Zep
Graph search `zep_graph_search`	Perform hybrid graph search combining semantic similarity and BM25 full-text search across the
List groups ordered `zep_list_groups_ordered`	Retrieve all groups from Zep with pagination support
List sessions ordered `zep_list_sessions_ordered`	Retrieve all sessions from Zep with pagination and ordering support
List threads `zep_list_threads`	Retrieve all threads from Zep with pagination support
List users ordered `zep_list_users_ordered`	Retrieve all users from Zep with pagination support
Add fact triple `zep_add_fact_triple`	Add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph
Add session memory `zep_add_session_memory`	Add memory messages to a specified Zep session
Add thread messages `zep_add_thread_messages`	Add chat messages to a thread in Zep and ingest them into the user knowledge graph
Clone graph `zep_clone_graph`	Clone a user or group graph with new identifiers in Zep
Create graph `zep_create_graph`	Create a new graph by adding data to Zep
Create group `zep_create_group`	Create a new group in Zep for multi-user graph management
Create session `zep_create_session`	Create a new session in Zep for storing conversation memory
Create thread `zep_create_thread`	Create a new thread in Zep for a specific user

Try it: find the Zep tool you need

Browse the 30 Zep tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Zep, summarize it in plain English, and point out anything that needs attention.

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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Zep working from chat.

	Manual	ClawLink
Credential handling	Collect, validate, store, and rotate the Zep API key yourself, then make sure every tool call uses the right account.	Users complete the hosted ClawLink setup once and the connected Zep 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 Zep.	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 Zep actions to the runtime in a format your agent can reliably use.	41 tools for Zep are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Zep 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 Hermes Agent users instead. You install the plugin once, connect Zep in the browser, and the 41 tools above work from chat. There is no SDK and no config file, and the Zep 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

Hermes paired but still can't use Zep

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Connection succeeds but no tools appear

Reconnect Zep 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 Zep tools

Zep 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 Zep 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.

Zep 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 Zep has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Hermes Agent Zep integration?

Yes. ClawLink is the fastest way to connect Hermes to Zep: link your Zep account once in the browser and Hermes Agent can call the Zep API through 41 ready-made tools — no custom code or token handling.

How do I connect Zep to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Zep in the dashboard and Hermes can use it from the next message — no config files, and the Zep key you paste is stored server-side instead of in your environment.

How long does it take to connect Zep to Hermes Agent?

About two minutes. Sign in, click Connect next to Zep in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Zep up myself?

Hermes paired but still can't use Zep

How to connect Zep to Hermes Agent

Setup

Install and pair

Connect Zep

Use it from chat