Memory Py MCP Server

Connect Memory Py to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A complete Python port of the official TypeScript MCP memory server. This server provides knowledge graph storage and retrieval capabilities via the Model Context. The memory py mcp server is what makes that connection.

What the server does

• Complete Knowledge Graph Management — Store and manage entities, relations, and observations
• JSONL File Format — Compatible with the TypeScript version's file format
• 9 MCP Tools — Full feature parity with the original TypeScript implementation
• Search Capabilities — Query entities by name, type, or observation content
• Graph Traversal — Explore entity connections and relationships
• Environment Configuration — Customizable storage location

Available tools

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

• Prerequisites — The Prerequisites tool exposed by this server
• Contributing — 1. Maintain compatibility with the TypeScript version 2. Follow Python best practices and PEP 8 3. Add comprehensive error handling 4. Update

Credentials and setup notes

Configuration is passed through the environment: MEMORY_FILE_PATH. 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.

• Python 3.8 or higher - macOS (tested platform)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Memory Py's toolset — Prerequisites, Contributing — is a fair guide to whether it matches your workflow. It is maintained by jason-c-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Memory Py's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.