Agent Skills
In addition to the MCP server config, we strongly recommend adding an Agent Skills file (SKILL.md) that teaches your IDE agent when and how to use the Memori MCP tools.
Why Add a Skills File
- Reliability — the agent consistently chooses between precise recall, broad summaries, durable augmentation, feedback, signup, and quota checks
- Lower prompt friction — you don't need to re-explain the memory workflow every session
- Focused context — most clients only load the full skill instructions when the skill is triggered
The SKILL.md File
Create a SKILL.md file from the canonical source:
This file teaches the agent the current Memori MCP decision flow:
- Use
memori_recallfor exact prior facts, preferences, decisions, and constraints. - Use
memori_recall_summaryfor broad session state, daily briefs, project overviews, and status recovery. - Use
memori_advanced_augmentationafter a response only for durable facts, preferences, or project context. - Use
memori_feedback,memori_signup, andmemori_quotaonly when the user request or a Memori error makes them relevant. - Skip Memori tools for trivial turns, ephemeral data, secrets, raw logs, and routine session activity.
Installing Skills by Client
Cursor
Cursor supports skill folders containing a SKILL.md:
- Project (recommended for teams):
.cursor/skills/memori-mcp/SKILL.md - Personal (all projects):
~/.cursor/skills/memori-mcp/SKILL.md
mkdir -p .cursor/skills/memori-mcp
# Add SKILL.md content to .cursor/skills/memori-mcp/SKILL.md
Restart Cursor so it re-discovers skills.
Claude Code
Claude Code skills live in either:
- Personal:
~/.claude/skills/memori-mcp/SKILL.md - Project:
.claude/skills/memori-mcp/SKILL.md
mkdir -p .claude/skills/memori-mcp
# Add SKILL.md content to .claude/skills/memori-mcp/SKILL.md
Restart Claude Code or reload the session.
OpenAI Codex
Codex scans repo-level skills under .agents/skills:
mkdir -p .agents/skills/memori-mcp
# Add SKILL.md content to .agents/skills/memori-mcp/SKILL.md
Restart Codex if it doesn't pick up changes automatically.
Warp
Warp supports custom agent rules that serve the same purpose as a skills file. Add the SKILL.md content to your Warp rules configuration:
- Project:
.warp/rules/memori-mcp.md - Global:
~/.warp/rules/memori-mcp.md
mkdir -p .warp/rules
# Add SKILL.md content to .warp/rules/memori-mcp.md
Restart Warp so the rules take effect.
Antigravity
Antigravity skills can be stored at:
- Workspace:
<workspace>/.agent/skills/memori-mcp/SKILL.md - Global:
~/.gemini/antigravity/skills/memori-mcp/SKILL.md
mkdir -p .agent/skills/memori-mcp
# Add SKILL.md content to .agent/skills/memori-mcp/SKILL.md
LangChain
LangChain agents use Memori MCP to persist user preferences and project context across invocations. The integration logic lives in your application layer using the langchain-mcp-adapters package.
To implement this, instantiate MultiServerMCPClient per request with the end-user's ID set as X-Memori-Entity-Id, as shown on the Client Setup page.
Slack
A Slack bot backed by an LLM uses Memori MCP to persist user preferences across all channels. As Slack is a cloud based service, the integration logic lives in your bot's backend.
To implement this, set the headers dynamically in your server's outgoing MCP tool calls using the Slack User ID from the incoming event payload as shown on the Client Setup page.
Notion
Custom Notion integrations use Memori MCP to maintain a consistent memory of a user's writing style and project context across different pages and databases.
To implement this, your middleware must map the Notion User ID to the Memori headers as shown on the Client Setup page. This ensures that regardless of which workspace or page the user is on, the AI assistant retrieves the same persistent preferences.
How It All Works Together
Once both the MCP config and skills file are installed:
- The MCP config ensures the Memori tools exist (
memori_recall,memori_recall_summary,memori_advanced_augmentation,memori_feedback,memori_signup, andmemori_quota) - The skills file ensures the agent uses them consistently and correctly — recall or summarize when prior context matters, augment only durable context, and skip memory for ephemeral turns