mem0 Connector for Muse
Persistent memory layer: store, search, and manage memories.
- What
- Persistent memory layer: store, search, and manage memories.
- Cost
- Free
- Needs
- A mem0 API key (created at app.mem0.ai — keys look like `m0-...`), kept in your Muse's secure vault (never paste secrets here). Note: add, delete, and especially wipe are writes — confirm before running them; the free Hobby tier covers 10k adds + 1k retrievals per month.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that manages your mem0 memory layer: store memories extracted from messages, run semantic search over them, and handle the full lifecycle (list, read, get one, change history, delete) scoped by user, agent, app, or run. Add and search are async — they return an event id you poll until success; never invent memory contents before the poll succeeds. Honest note: mem0 v3 add is add-only (it does not auto-update or auto-delete older conflicting memories), so search first when a fact may already exist. `wipe` deletes every memory in the scope — always confirmed. The free Hobby tier covers 10k add requests + 1k retrieval requests per month. Draft: written from mem0's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A mem0 API key (created at app.mem0.ai — keys look like `m0-...`), kept in your Muse's secure vault (never paste secrets here). Note: add, delete, and especially wipe are writes — confirm before running them; the free Hobby tier covers 10k adds + 1k retrievals per month. No GitHub account needed unless listed here. Install "mem0 Connector for Muse" for me. A Muse agent skill that manages your mem0 memory layer: store memories from messages, semantic search, full lifecycle management. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/mem0 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mem0". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my mem0 API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.