Cursor

Memstate + Cursor

Give Cursor structured memory that persists across sessions and projects.

Cursor's AI forgets everything between sessions. Memstate gives Cursor a persistent memory layer via MCP — your tech stack, architecture decisions, and project context are always available, never re-explained.

1

Get Your API Key

Sign up for free at Memstate AI and create an API key from your dashboard. No credit card required.

Sign Up Free

Already have an account? Go to API Keys →

2

Add MCP Configuration

Add the following to your Cursor MCP configuration file. Replace YOUR_API_KEY_HERE with your key.

MCP Configuration (JSON)
{
  "mcpServers": {
    "memstate": {
      "command": "npx",
      "args": ["-y", "@memstate/mcp"],
      "env": {
        "MEMSTATE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

📁 Where to put this config:

Project.cursor/mcp.json (in your project root)
Global~/.cursor/mcp.json
3

Choose Project or Global Scope

Cursor supports MCP at two scopes. Choose the one that fits your workflow:

Project-scoped (recommended)

.cursor/mcp.json

Memory is scoped to this project. Commit this file to share Memstate setup with your team.

Global

~/.cursor/mcp.json

Available across all your Cursor projects.

Cursor Settings UI

You can also add MCP servers via Cursor Settings → MCP → Add Server, then paste the config JSON.

4

Add Agent Instructions

Paste this into your project's AGENTS.md, CLAUDE.md, or GEMINI.md. This tells your agent how to use Memstate automatically.

AGENTS.md (paste into your project)
# Memstate MCP - Memory Storage
This project uses Memstate MCP for versioned memory. Keypaths are hierarchical (e.g. `project.myapp.database`).

## Which tool when
- **memstate_remember** — PREFERRED for markdown, task summaries, meeting notes. Server extracts keypaths automatically.
- **memstate_set** — Only for single keypath = single short value (e.g. config.port).
- **memstate_get** — Browse project, fetch existing knowledge before tasks.
- **memstate_search** — Find by meaning when you don't know the keypath.
- **memstate_history** — View version history of a keypath.

## Before each task
Check what already exists: `memstate_get(project_id="myproject")`

## After each task
Save a summary: `memstate_remember(project_id="myproject", content="## Summary\n- What was done\n- Key decisions", source="agent")`

Why this matters

Without instructions, your agent won't know to use Memstate proactively. This snippet tells it to check existing memories before tasks and save summaries after — keeping your project context current across every session.

Verify the Connection

Restart Cursor, then ask your agent:

Test prompt
Use memstate_get() to list all my projects and confirm Memstate is connected.

You're all set!

Cursor now has access to structured, versioned memory. It will automatically look up existing knowledge before tasks and save summaries after completion — keeping your project context current and organized across every session.

Alternative: Install as an Agent Skill

Prefer a portable, project-committed approach? Install the Memstate skill directly into your repo. Skills are loaded automatically by compatible agents (Claude Code, Cline, Cursor) without needing manual AGENTS.md edits.

Terminal
npx @memstate/skills setup

See the Skills documentation for full details on supported agents and manual installation options.