memories-mcp
npx skills add https://github.com/webrenew/memories --skill memories-mcp
Agent 安装分布
Skill 文档
memories-mcp
Connect AI agents to the memories.sh memory layer via MCP (Model Context Protocol).
The CLI is the primary interface for memories.sh â use
memories generateto create native config files for each tool. The MCP server is a fallback for real-time access when static configs aren’t enough. It’s also the best choice for browser-based agents (v0, bolt.new, Lovable) where the CLI can’t run.
Quick Start
# Local stdio transport (most reliable)
memories serve
# HTTP/SSE transport (for web clients like v0)
memories serve --sse --port 3030
# Cloud-hosted (no local install needed)
# Endpoint: https://memories.sh/api/mcp
# Header: Authorization: Bearer YOUR_KEY
Primary Tool: get_context
Always start with get_context â it returns active rules + relevant memories in one call:
get_context({ query: "authentication flow" })
â ## Active Rules
â - Always use TypeScript strict mode
â ## Relevant to: "authentication flow"
â ð¡ DECISION (P) abc123: Chose JWT for stateless auth
Leave query empty to get just rules. Use limit to control memory count (default: 10).
When relationship extraction is enabled server-side, get_context may also return conflicts[] for contradiction-linked memories. Treat these as clarification prompts before taking irreversible actions.
Tool Selection Guide
| Goal | Tool | When |
|---|---|---|
| Start a task | get_context |
Beginning of any task â gets rules + relevant context |
| Save knowledge | add_memory |
After learning something worth persisting |
| Resolve contradictory context | get_context |
If conflicts[] is present, ask a disambiguating question and persist the answer |
| Find specific info | search_memories |
Full-text search with prefix matching |
| Browse recent | list_memories |
Explore what’s stored, filter by type/tags |
| Get coding standards | get_rules |
When you only need rules, not memories |
| Update a memory | edit_memory |
Fix content, change type, update tags |
| Remove a memory | forget_memory |
Soft-delete (recoverable) |
| Bulk remove memories | bulk_forget_memories |
Filtered mass soft-delete by type, tags, age, pattern |
| Reclaim storage | vacuum_memories |
Permanently purge all soft-deleted records |
| Add reminder (local) | add_reminder |
Create cron-based reminder in local CLI DB |
| Run reminders (local) | run_due_reminders |
Emit due reminders and advance schedule |
| Manage reminders (local) | list_reminders, enable_reminder, disable_reminder, delete_reminder |
Inspect and control reminder lifecycle |
Memory Types
When using add_memory, pick the right type:
- rule â Coding standards, preferences, constraints (always returned by
get_context) - decision â Architectural choices with rationale
- fact â Project-specific knowledge (API limits, env vars, etc.)
- note â General notes (default)
- skill â Reusable agent workflows (use with
categoryandmetadata)
Scopes
- project (default) â Scoped to current git repo, detected automatically
- global â Applies everywhere, set
global: trueinadd_memory - project override â Set
project_id: "github.com/org/repo"inadd_memory(orstart_memory_stream) to force project scope when the MCP process is running outside that repo
Do not send both global: true and project_id in the same call.
Streaming Memory Tools
For collecting content from SSE sources (v0 artifacts, streaming responses):
start_memory_stream({ type?, tags?, global?, project_id? })â returnsstream_idappend_memory_chunk({ stream_id, chunk })(repeat for each piece)finalize_memory_stream({ stream_id })â creates memory + triggers embeddingcancel_memory_stream({ stream_id })â discard if aborted
MCP Resources
For clients that support MCP resources:
| URI | Content |
|---|---|
memories://rules |
All active rules as markdown |
memories://recent |
20 most recent memories |
memories://project/{id} |
Memories for a specific project |
Transport Options
| Transport | Use Case | Command |
|---|---|---|
| stdio | Claude Code, Cursor, local tools | memories serve |
| HTTP/SSE | v0, web-based agents, remote | memories serve --sse --port 3030 |
| Cloud | No local install, cross-device | https://memories.sh/api/mcp + Authorization: Bearer KEY |
Reminder tools are local CLI MCP only (memories serve).
Reference Files
- Client setup configs: See references/setup.md for copy-paste configs for every supported client
- Full tool reference: See references/tools.md for all parameters, return formats, and examples