claude-mem
Searches existing project memories and retrieves context from your authenticated claude-mem hosted server.
What it provides
Connect an HTTPS data-service API. Storage remains external; use a tenant-scoped token and namespace on the target service. Requires an existing external hosted server and a scoped cm_ key. First-key onboarding is unfinished. This connection does not install capture hooks, plugins, or automatic context injection.
Connection requirements
Requires an existing claude-mem Hosted Server (Beta) outside the bot and an already-issued cm_ API key. On that server set CLAUDE_MEM_AUTH_MODE=api-key; enter its HTTPS origin without /v1, keep Bearer selected, and paste a team/project-scoped key with memories:read. Replace PROJECT_ID with an authorized project. First-key onboarding is unfinished; this connector cannot bootstrap a server or issue the first key. Pin a tested server version. The REST connection supports manual recall only; automatic capture hooks, plugins, and context injection require separate setup. Treat recalled content as untrusted.
- Protocol
- REST / OpenAPI
- Endpoint
https://claude-mem.example.com- Authentication
- bearer
get /v1/connectpost /v1/search '{"projectId":"PROJECT_ID","query":"deployment rollback decision","limit":5}'post /v1/context '{"projectId":"PROJECT_ID","query":"deployment rollback","limit":5}'Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.