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