ClawLink

How to connect Supermemory to Hermes Agent

Connect Supermemory to Hermes with ClawLink: paste your Supermemory key once and 86 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Supermemory
Supermemory
SupermemoryAPI KEYMCP

Supermemory is a memory and context API for ingesting, organizing, searching, and recalling information across applications.. Once connected, Hermes Agent can read and act on Supermemory from chat — pairing, token refresh, and tool wiring handled for you.

86 tools

Most guides for giving Hermes Agent Supermemory 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 Supermemory setup: pair once in the browser and your always-on Hermes agent can act on Supermemory 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 Supermemory.

  1. 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. 2

    Connect Supermemory

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Supermemory?"

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 Supermemory in the ClawLink dashboard — paste your Supermemory API key once.

Verify the connection by asking Hermes:

Use Supermemory to count namespace document memories and walk me through the result in plain English.

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 Supermemory is connected in the dashboard, that agent calls the same 86 Supermemory tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Supermemory MCP for Hermes

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

What the Hermes Agent Supermemory integration can do

86 Supermemory 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 86.

30 of 86 Supermemory tools for Hermes

ToolWhat it does
Count namespace document memories supermemory_count_namespace_document_memoriesCount live memories in a namespace for up to 100 public document IDs
Get account status supermemory_get_account_statusReturn the connected Supermemory organization's plan, credit balance, high-level usage, and
Get automatic topups supermemory_get_automatic_topupsDeprecated legacy v3 API, scheduled to shut down December 31, 2026
Get billing usage supermemory_get_billing_usageDeprecated legacy v3 API; provider shutdown is December 31, 2026
Get billing usage events supermemory_get_billing_usage_eventsDeprecated legacy v3 API, scheduled to shut down December 31, 2026
Get connection supermemory_get_connectionDeprecated by the provider: this legacy v3 endpoint shuts down December 31, 2026
Get connector supermemory_get_connectorRead a connector in a namespace, including its setup, selection, and latest sync status
Get container tag supermemory_get_container_tagDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
Get container tag merge supermemory_get_container_tag_mergeDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
Get document supermemory_get_documentGet one document's content, metadata, source details, and processing status by document ID
Get document chunks supermemory_get_document_chunksReturn the ordered extracted chunks for one processed document
Get document file URL supermemory_get_document_file_urlDeprecated by the provider: this legacy endpoint shuts down December 31, 2026
Get error analytics supermemory_get_error_analyticsDeprecated legacy v3 endpoint scheduled to shut down December 31, 2026
Get namespace supermemory_get_namespaceRead a namespace's supporting context and lifecycle timestamps
Get namespace document supermemory_get_namespace_documentRetrieve a document's canonical content, metadata, and processing state by document ID or
Get namespace memory supermemory_get_namespace_memoryRetrieve one memory by ID within a namespace, including its text, metadata, version, and recall
Get namespace profile supermemory_get_namespace_profileRead the continuously maintained profile of a namespace's subject without a search query
Get namespace profile buckets supermemory_get_namespace_profile_bucketsInspect the profile taxonomy active in a Supermemory namespace
Get organization supermemory_get_organizationRead the connected organization's shared background that guides memory formation across all
Get profile supermemory_get_profileRetrieve the static, dynamic, or bucketed profile learned for one container tag, optionally
Get profile buckets supermemory_get_profile_bucketsDeprecated by the provider: this legacy v4 endpoint shuts down on December 31, 2026
Get provider connection supermemory_get_provider_connectionDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
Get settings supermemory_get_settingsDeprecated legacy v3 API, scheduled to shut down December 31, 2026
Get usage analytics supermemory_get_usage_analyticsDeprecated legacy v3 API, scheduled to shut down December 31, 2026
List all connectors supermemory_list_all_connectorsList one page of connectors across every namespace the API key can read, optionally filtered by
List connection documents supermemory_list_connection_documentsDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
List connection resources supermemory_list_connection_resourcesDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
List connections supermemory_list_connectionsDeprecated by the provider: this legacy v3 endpoint shuts down on December 31, 2026
List connectors supermemory_list_connectorsList one page of connectors that sync into a namespace, optionally filtered by provider
List container tags supermemory_list_container_tagsDeprecated by the provider: the legacy v3 API shuts down December 31, 2026

Try it: find the Supermemory tool you need

Browse the 30 Supermemory tools

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

Example prompts

Use Supermemory to count namespace document memories and walk me through the result in plain English.

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 Supermemory working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Supermemory API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Supermemory account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Supermemory.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Supermemory actions to the runtime in a format your agent can reliably use.86 tools for Supermemory are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Supermemory 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 Supermemory in the browser, and the 86 tools above work from chat. There is no SDK and no config file, and the Supermemory 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 Supermemory

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 Supermemory 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 Supermemory tools

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

Supermemory 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 Supermemory 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 Supermemory integration?

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

How do I connect Supermemory 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 Supermemory in the dashboard and Hermes can use it from the next message — no config files, and the Supermemory key you paste is stored server-side instead of in your environment.

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

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

Why use ClawLink instead of wiring Supermemory up myself?

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 Supermemory working from chat.

Hermes paired but still can't use Supermemory

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.

On this page