Mneme as the memory + intent layer for MetaMask Agentic Wallet. Six open-source skills that plug your agent's persistent memory into MetaMask's guardrailed execution rail.
Mneme is an agent-native database on Base — eight primitives (memory · graph · streams · chat · dreams · beam · mesh · mandate) in one Postgres schema. MetaMask Agentic Wallet is the execution layer for autonomous on-chain action — guardrails, Transaction Shield, MEV protection, 25+ EVM chains and HyperLiquid.
This skill pack is the seam. Same code shape we already ship for other agent frameworks, MIT-licensed, ready to drop into the MetaMask Agentic Wallet CLI on day one of public launch.
| Skill | What it does |
|---|---|
mneme-context-before-trade |
Before a swap / send / LP / perp / predict, pull the agent's relevant memories, dreams, and recent stream events from Mneme so the trade decision is grounded in memory rather than pulled from the LLM's prior. |
mneme-log-trade |
After MetaMask executes, write the result back to Mneme — tx_hash, gas, P&L delta, slippage, contract, protocol — as an INSERT into your schema's events (or a custom trades) table. Every action queryable later. |
mneme-mandate-create |
Translate the operator's natural-language plan ("DCA into MNEME on a 5% dip, $1k cap, uniswap-v3 only") into a Mneme Mandate row, ready to arm. |
mneme-mandate-arm |
Move a pending mandate to armed and let the Mneme worker watch the conditions. When conditions trip, the mandate is dispatched to MetaMask Agentic Wallet. |
mneme-watch-condition |
Subscribe to a Base contract event via Mneme Streams. When the event fires (transfer, swap, mint, custom), the skill can trigger downstream mandates or notifications. |
mneme-recap |
Daily / hourly recap of every executed trade — pulls from the same events table, summarizes via Mneme /chat (schema-aware Claude), notifies through whatever channel your CLI uses. |
| Layer | Mneme provides | MetaMask provides |
|---|---|---|
| Memory | memories, documents, entities, relations, dreams tables — vector + graph + hybrid retrieval |
— |
| Live awareness | Mneme Streams (Base events auto-INSERT into your schema) | — |
| Intent | Mneme Mandate (declarative intents with guardrails, status lifecycle) | — |
| Execution | wallet adapter → MetaMask Agentic Wallet API | spend limits · allowed protocols · risk profile · Transaction Shield · MEV protection · 25+ chains |
| Write-back | Auto-INSERT into events table, ticked via Mneme Beam (SSE) |
tx hash + status callback |
Mneme decides what to do and remembers. MetaMask decides how to safely do it. Neither layer leaks into the other.
Note: MetaMask Agentic Wallet is currently in early access (public launch summer 2026). This pack is published in advance so it's plug-and-play on day one. The skills compile and pass linting today, and the Mneme side of every skill is already live at
https://gateway.mnemedb.dev.
When the MetaMask CLI ships:
metamask plugins enable mneme
metamask mneme initThe init wizard prompts for your MNEME_API_KEY (get one at mnemedb.dev → API Keys, scope *) and your default wallet_provider (metamask).
export MNEME_API_KEY=mneme_sk_...
export MNEME_GATEWAY=https://gateway.mnemedb.dev # defaultEvery skill checks MNEME_API_KEY first and fails fast if missing. MetaMask Agentic Wallet auth follows whatever the official CLI defines — we never touch your private key.
MIT — see LICENSE.
- Mneme: mnemedb.dev · mnemedb.dev/metamask · docs · github.com/mnemedb/mnemedb
- MetaMask Agentic Wallet: metamask.io/agent-wallet
Mneme remembers. MetaMask executes. Both stay in their lane.