메뉴
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
| name | agentmemory-mcp-tools |
| description | Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP. |
| user-invocable | false |
agentmemory exposes its full capability set as MCP tools. This skill is the index: it tells you which tool to reach for and where to find exact parameters.
Save then recall:
memory_save with content (the insight), concepts (comma-separated keywords), files (comma-separated paths).memory_smart_search with query and limit to retrieve it later. This runs hybrid BM25 plus vector plus graph-expanded search.memory_save, memory_observe flows, memory_compress_file.memory_smart_search, memory_recall, memory_file_history, memory_timeline, memory_vision_search.memory_sessions, memory_commits, memory_commit_lookup.memory_lesson_save, memory_lesson_recall, memory_graph_query, memory_relations, memory_patterns, memory_crystallize.memory_slot_create, memory_slot_append, memory_slot_get, memory_slot_list, memory_slot_replace, memory_slot_delete.memory_governance_delete, memory_audit, memory_verify, memory_heal, memory_diagnose.memory_smart_search for open recall, memory_recall when you already have a focused query, memory_sessions for session listings.Full tool table with parameters and the core-set marking lives in REFERENCE.md, generated from source so it never drifts.