Cursor currently has a one-click deeplink install button and an automem.mdc rule for recall/store, but this needs to be reviewed and made "proper" — i.e. verify it holds up to the same standard as Claude Desktop/Claude Code support.
Possible scope:
- Confirm the deeplink install config is current and correctly points at the right endpoint/API key flow
- Review
automem.mdc rule content for completeness (recall on session start, store triggers, etc.)
- Add/verify guided install (
npx @verygoodplugins/mcp-automem install) fully configures Cursor, not just prints a snippet
- Add a Cursor-specific walkthrough/screenshot to INSTALLATION.md if missing
- Test end-to-end on a fresh Cursor install
Flagged by Jack — wants Cursor to be a first-class, no-friction setup path like Claude Code.
Cursor currently has a one-click deeplink install button and an
automem.mdcrule for recall/store, but this needs to be reviewed and made "proper" — i.e. verify it holds up to the same standard as Claude Desktop/Claude Code support.Possible scope:
automem.mdcrule content for completeness (recall on session start, store triggers, etc.)npx @verygoodplugins/mcp-automem install) fully configures Cursor, not just prints a snippetFlagged by Jack — wants Cursor to be a first-class, no-friction setup path like Claude Code.