A side-by-side look at the Codeagent Memory and Prism MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codeagent Memory for knowledge & memory work; choose Prism MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | C Codeagent Memory | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 33/100 · Emerging | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | 158 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Codeagent Memory | View Prism MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Codeagent Memory yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"dcostenco-prism-mcp": {
"command": "npx",
"args": [
"-y",
"prism-mcp-server"
]
}
}
}