Add memory to Cursor

Cursor speaks MCP, so giving its agent persistent memory is a few lines in an mcp.json file. Add the server, reload, and Cursor can store and recall named memory across sessions and projects.

What you get

Persistent memory that survives across Cursor sessions and projects: named values you store once and recall later, shared memory for multi-agent work, temporal memory for facts that change over time, and no vector database to run. It is fifteen tools in total, and they show up as tools Cursor's agent calls directly. For the concepts underneath, see the MCP integration overview.

Prerequisites

• An AgentRAM API key. Create one free.
• Cursor installed (0.45 or newer), and Node.js 18+ (node -v).

Add the server

Cursor reads MCP servers from an mcp.json file. Use a global file to make AgentRAM available in every project, or a project file to scope it to one repo:

• Global (every project): ~/.cursor/mcp.json. On Windows, %USERPROFILE%\.cursor\mcp.json.
• Project only: .cursor/mcp.json in the repo root.

Add this block to whichever file you chose:

{
  "mcpServers": {
    "agentram": {
      "command": "npx",
      "args": ["-y", "agentram-mcp"],
      "env": { "AGENTRAM_API_KEY": "agentram_your_key_here" }
    }
  }
}

Prefer the UI? Open Cursor Settings, go to Tools & MCP, click Add new MCP server, and paste the same block. If your install has an Enable MCP servers toggle, make sure it is on.

If you commit a project .cursor/mcp.json to version control, do not hardcode your key there. Keep the real key in a global file or an environment variable instead. Config paths and the settings layout can shift between Cursor versions; if the server does not appear, check Cursor's current MCP docs. The server command and env var stay the same.

Quick start

Reload the Cursor window so it picks up the server, then in the agent chat try:

Store my test command as "npm run test:ci" under the key test_cmd.

Later, in a new session:

Recall test_cmd from AgentRAM.

It reads the value back instead of starting from nothing. To see the temporal side, ask it to store a fact that changes, like a plan or a status, update it later, and then ask for the history.

Smoke test and troubleshooting

• Tools do not appear. Reload the Cursor window after editing mcp.json, then open Settings, Tools & MCP, and confirm agentram shows a green dot. If there is an Enable MCP servers toggle, make sure it is on.
• 401 or auth error. Check AGENTRAM_API_KEY is set correctly in the config and starts with agentram_.
• npx cannot find agentram-mcp. Node is older than 18, or you are offline. Check node -v.
• Want the raw logs? Open the Output panel (Cmd+Shift+U on macOS, Ctrl+Shift+U on Windows) and pick MCP from the dropdown.