Synap Memory vs Engram
A side-by-side look at the Synap Memory and Engram MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Synap Memory for knowledge & memory work as a local process; choose Engram 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 Synap Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 44/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 77 | 19 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Synap Memory | View Engram |
Tools & capabilities
Synap Memory tools
No tool names declared yet. Check the project README from the listing page.
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
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.
Synap Memory
{
"mcpServers": {
"synap-memory": {
"command": "uvx",
"args": [
"maximem-synap"
]
}
}
}
Engram
{
"mcpServers": {
"engram-2": {
"command": "npx",
"args": [
"-y",
"@getengram/cli"
]
}
}
}
Frequently asked questions
Synap Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Engram belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Synap Memory for knowledge & memory work and Engram 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.
Synap Memory has no declared pricing — check the project's own site. Engram has no declared pricing — check the project's own site. 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 synap-memory and engram-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Synap Memory has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 77 GitHub stars. Engram has 57/100 (Good) with 2 views, 0 installs and 19 GitHub stars.