Engram vs Basic Memory
A side-by-side look at the Engram and Basic Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Engram for knowledge & memory work as a local process; choose Basic Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Engram when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_conversation, append_messages, search.
Choose Basic Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
bm_write, bm_read, bm_edit.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 19 | 4,348 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 13 |
| Full listing | View Engram | View Basic Memory |
Tools & capabilities
Engram tools 6
create_conversationStart a new conversation with optional title, tags, metadataappend_messagesAdd messages to an existing conversationsearchSemantic search across all conversationsget_conversationRetrieve a conversation with its messageslist_conversationsList conversations with filtering and paginationdelete_conversationRemove a conversation and its data
Basic Memory tools 13
bm_writebm_readbm_editbm_movebm_deletebm_searchbm_listbm_findbm_contextbm_mansearchfetch- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Engram
{
"mcpServers": {
"engram-2": {
"command": "npx",
"args": [
"-y",
"@getengram/cli"
]
}
}
}
Basic Memory
{
"mcpServers": {
"basicmachines-co-basic-memory": {
"command": "uvx",
"args": [
"--prerelease=allow",
"basic-memory"
]
}
}
}
Frequently asked questions
Engram is categorized under Knowledge & Memory and uses a local stdio subprocess. Basic Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Engram for knowledge & memory work and Basic Memory for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Engram has no declared pricing — check the project's own site. Basic Memory is listed as freemium — a free tier with paid plans. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add engram-2 and basicmachines-co-basic-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Engram has a quality signal of 57/100 (Good) with 2 views, 0 installs and 19 GitHub stars. Basic Memory has 64/100 (Good) with 2 views, 0 installs and 4,348 GitHub stars.