Memwright MCP Server

Embedded memory for AI agents with SQLite FTS5, pgvector, and Neo4j graph search.

Remote serverstreamable-httpPython

What is the Memwright MCP server?

Connect Memwright to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Embedded memory for AI agents with SQLite FTS5, pgvector, and Neo4j graph search. The memwright mcp server is what makes that connection.

What the server does

Full-context replay re-reads the whole conversation every turn — input tokens that grow O(n²) and a bill that compounds with every session. Attestor retrieves only what's needed: flat ~200 tokens per call, 21× fewer input tokens by turn 100, 100% recall — measured across six models, open and closed.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Multi — agent products where many LLMs write to the same memory store
  • Self — hosted deployments — your VPC, your Postgres, your Neo4j
  • Version — 4.1.6 (stable; greenfield rebuild — no v3 migration path)
  • PyPI — attestor
  • Import — attestor
  • Repohttps://github.com/bolnet/attestor
  • Turn — Full-context replay
  • t24 — growing
  • t50 — growing
  • t100 — 8,709 tok/call
  • Registry — Pull address
  • GHCR — ghcr.io/bolnet/attestor:latest

Credentials and setup notes

Configuration is passed through the environment: OPENROUTER_API_KEY, PINECONE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Plenty of database access 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. Memwright's toolset — Multi, Self, Version and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bolnet; 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.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Memwright.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Multiagent products where many LLMs write to the same memory store
Selfhosted deployments — your VPC, your Postgres, your Neo4j
Version4.1.6 (stable; greenfield rebuild — no v3 migration path)
PyPIattestor
Importattestor
Repo<https://github.com/bolnet/attestor>
TurnFull-context replay
t24growing
t50growing
t1008,709 tok/call
RegistryPull address
GHCRghcr.io/bolnet/attestor:latest
Quayquay.io/bolnet/attestor:latest
ContainerRole

How to install the Memwright MCP server

{
  "mcpServers": {
    "memwright": {
      "command": "uvx",
      "args": ["attestor"],
      "env": {
        "OPENROUTER_API_KEY": "your-value",
        "PINECONE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OPENROUTER_API_KEYCredential the server authenticates with.Yes
PINECONE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Memwright to Multi.
  • Use Memwright to Self.
  • Use Memwright to Version.

Frequently asked questions

It connects Memwright to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Multi, Self, Version, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memwright directly.