Memory MCP Server
[](https://mseep.ai/app/evangstav-python-memor
What is the Memory MCP server?
# Memory MCP Server A Model Context Protocol (MCP) server that provides. That is what the memory mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The tools it exposes
The server publishes 5 tools. What each one is for:
Observations— The Observations tool exposed by this serverRelations— The following relation types are supported: - knows: Person to person connection - contains: Parent/child relationship - uses: Entity utilizingEntityResponse— The EntityResponse tool exposed by this serverGraphResponse— The GraphResponse tool exposed by this serverOperationResponse— The OperationResponse tool exposed by this server
What it needs from you
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.
Getting it running
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
How it compares
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's toolset — Observations, Relations, EntityResponse and 2 more — is a fair guide to whether it matches your workflow. It is maintained by evangstav; 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.
Things to watch
- 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.
Available tools
| Tool | What it does |
|---|---|
| Observations | The Observations tool exposed by this server. |
| Relations | The following relation types are supported: - knows: Person to person connection - contains: Parent/child relationship - uses: Entity utilizing another entity - created: Authorship/creation relationship - belongs-to: Mem |
| EntityResponse | The EntityResponse tool exposed by this server. |
| GraphResponse | The GraphResponse tool exposed by this server. |
| OperationResponse | The OperationResponse tool exposed by this server. |
Configuration
| Variable | Description | Required |
|---|---|---|
| MEMORY_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
Example prompts to try
- “Use Memory to Observations.”
- “Use Memory to Relations.”
- “Use Memory to EntityResponse.”
Frequently asked questions
Alternatives to the Memory MCP server
Memory
OfficialA knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Context7
OfficialKill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Notion
OfficialYour workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Sequential Thinking
OfficialA structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Serena
OfficialSymbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Obsidian
Chat with your second brain — search, read and write vault notes through the Local REST API.