Sessionmem MCP Server

Local-first MCP memory layer for coding agents across Claude Code, Codex, Cursor, Cline, Windsurf, and other MCP-compatible hosts.

Remote serverstreamable-httpTypeScript

What is the Sessionmem MCP server?

Sessionmem MCP server exists for a simple reason — assistants are far more useful when they can act on Sessionmem directly instead of describing what you should do. Local-first MCP memory layer for coding agents across Claude Code, Codex, Cursor, Cline, Windsurf, and other MCP-compatible hosts.

What you get

WITHOUT sessionmem: You explain the stack. The JWT bug from last week. The Stripe migration that's halfway done. The billing code to stay away from. Same questions. Different day.

What the assistant can call

Once Sessionmem is connected, these are the calls the assistant has available:

  • Cursor — Codex
  • Cline — Windsurf
  • Antigravity — QCoder

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need one environment variable: ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sessionmem's toolset — Cursor, Cline, Antigravity — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the sessionmem mcp server does with a few real requests.

Available tools

ToolWhat it does
CursorCodex
ClineWindsurf
AntigravityQCoder

How to install the Sessionmem MCP server

{
  "mcpServers": {
    "sessionmem": {
      "command": "npx",
      "args": ["-y", "sessionmem"],
      "env": {
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
ANTHROPIC_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Sessionmem to Cursor.
  • Use Sessionmem to Cline.
  • Use Sessionmem to Antigravity.

Frequently asked questions

It connects Sessionmem to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Cursor, Cline, Antigravity) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Sessionmem directly.