janjaszczak/cursor

mcp-memory-recall

Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repeated topic suggests existing decisions.

First seen Feb 21, 2026

Installation

$ npx skills add janjaszczak/cursor --skill mcp-memory-recall

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from janjaszczak/cursor · top by installs.

npx skills add janjaszczak/cursor

Browse all from janjaszczak/cursor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires MCP memory server configured in Cursor (e.g., Neo4j). Network access to MCP endpoint.
Allowed toolsMCP(*)
Declared agents cursor
More metadata
author
janjaszczak
intent
Reduce repeated context; avoid unnecessary “pre-flight” on trivial tasks.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,650 B
  • docs SUMMARY.md 281 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9 installs

SKILL.md

mcp-memory-recall

Activation gate (anti-noise)

Only run memory recall if at least one is true:

  • User explicitly references past work (“jak ostatnio”, “wróćmy do…”, “kontynuuj”).
  • The task is multi-step/refactor/migration where prior decisions materially affect correctness.
  • The user asks to “remember/check what we decided”.

Do NOT run for:

  • Single-shot Q&A, simple command request, or isolated conceptual question.

Procedure

  1. Query memory for: last relevant project node, decisions, constraints, open TODOs, and “lessons learned”.
  2. Extract only the minimum set needed to answer.
  3. If conflicts exist (new user constraints vs memory), prefer latest user instruction and mark memory as stale.
  4. In output, reference memory-derived constraints as “previously decided” (no verbose dump).

Output

  • Short: “What I found” (key constraints/decisions) + “How it affects this task” + next action.

Failure handling

  • If MCP memory is unavailable: proceed without it and mark as UNCERTAIN + suggest fastest way to verify (open MCP, rerun).