---
name: agent-memo-tools
description: Use the Agent Memo MCP to capture, retrieve, and maintain durable project context across agent sessions.
---

# Agent Memo Tools

Agent Memo is a remote MCP server for preserving useful context from agent work. Use it when work produces decisions, discoveries, progress, completed work, blockers, lessons, or unresolved questions that a future agent should know.

## Load this skill

The skill is hosted at `/skills/tools/SKILL.md`. Call the `skill` MCP tool without a path to discover this file and its references, then call it with a path to retrieve the Markdown content.

## Start of a task

1. Call `whoami` to confirm the authenticated user and profile.
2. Call `list_projects` to find the relevant project.
3. Call `get_project_context` before researching or changing an existing project.
4. Start a session with `start_session` when work belongs to a project.

Create a project with `create_project` only when no suitable project exists. Never pass a user ID; ownership comes from the authenticated MCP user.

## During work

Use `record_activity` for meaningful progress, discoveries, decisions, completed work, blockers, unresolved questions, and learnings. Keep titles concise and put useful detail in the body.

Use `save_memory` for durable knowledge that should survive the current session. Link it to the project and, when possible, the originating session and activity. Every write requires a fresh idempotency key of at least 8 characters.

See:

- `/skills/tools/references/capture.md` for capture workflows.
- `/skills/tools/references/retrieval.md` for finding existing context.
- `/skills/tools/references/memory-review.md` for resolving and editing memories.
- `/skills/tools/references/tool-reference.md` for complete tool inputs and limits.

## Before repeating work

Search existing knowledge with `search_memory` and inspect recent work with `get_recent_activity`. Use `list_unresolved` to find open questions before making a decision.

## Security and reliability

- The authenticated MCP identity is the only owner identity. Do not invent or submit a `user_id`.
- Do not store secrets, access tokens, or credentials in activities or memories.
- Use a new idempotency key for each intentional write and reuse the same key only when retrying the same payload.
- Preserve uncertainty as an unresolved activity or memory instead of presenting it as fact.