Cursor

Two install paths. The plugin is the recommended one: it registers 7 auto-capture hooks, all 17 skills, and the MCP server in one step, and works in both the Cursor IDE and the cursor-agent CLI. The connect path wires MCP only; capture is then tool-driven, steered by a project rule the connect command installs.

Full plugin

Start agentmemory

npx @agentmemory/agentmemory

Install the plugin

From the Cursor Marketplace once the listing is live, or point Cursor at a checkout today: clone the repo, then Cursor Settings → Plugins → install from the local directory. The manifest lives at .cursor-plugin/plugin.json.

Configure variables (optional)

AGENTMEMORY_URL and AGENTMEMORY_SECRET are declared as plugin variables and managed in Cursor’s plugin dashboard (Plugins → Configure). Leave them unset for a keyless localhost daemon.

Verify

Run any agent turn, then check the viewer at http://localhost:3113 — the session, your prompt, and each tool call should appear as observations.

What the plugin registers

Surface	Detail
Hooks	`sessionStart`, `beforeSubmitPrompt`, `preToolUse`, `postToolUse`, `postToolUseFailure`, `stop`, `sessionEnd` — sessions, prompts, tool runs, and failures capture automatically
Skills	All 17 skills, including the invocable `/recall`, `/remember`, `/lesson` set
MCP	The stdio `@agentmemory/mcp` shim, proxying all 54 tools when the daemon is reachable
Context injection	With `AGENTMEMORY_INJECT_CONTEXT=true` on the daemon, session start receives recalled project context via Cursor’s `additional_context` channel

preCompact is deliberately not wired: Cursor’s output contract for that event cannot carry injected context, so the hook would only log failures.

Cursor’s CLI print mode (cursor-agent -p) never fires the prompt-submit event, so the plugin backfills user prompts from the session transcript when the session ends. Content dedup drops the re-post in GUI sessions where the live hook already captured the prompt — capture behaves the same on both surfaces.

MCP only

Wire MCP

npx @agentmemory/agentmemory connect cursor

The adapter detects ~/.cursor/, backs up mcp.json, merges the entry, and verifies it after writing.

Restart Cursor

Restart Cursor, then check Settings, MCP: agentmemory should list its tools.

Without hooks there is no automatic capture: the agent calls memory_recall and memory_save itself, steered by the guideline rule connect installs. Prefer the plugin.

What connect writes

~/.cursor/mcp.json

{
  "mcpServers": {
    "agentmemory": {
      "command": "npx",
      "args": ["-y", "@agentmemory/mcp"],
      "env": {
        "AGENTMEMORY_URL": "${AGENTMEMORY_URL:-http://localhost:3111}",
        "AGENTMEMORY_SECRET": "${AGENTMEMORY_SECRET:-}",
        "AGENTMEMORY_TOOLS": "${AGENTMEMORY_TOOLS:-all}"
      }
    }
  }
}

Get started

Concepts

Connect

Integrations

Workflows

Full plugin

What the plugin registers

MCP only

What connect writes

​Full plugin

​What the plugin registers

​MCP only

​What connect writes

Full plugin

What the plugin registers

MCP only

What connect writes