Prism MCP vs MCP Memory Graph
A side-by-side look at the Prism MCP and MCP Memory Graph MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Prism MCP for knowledge & memory work as a local process; choose MCP Memory Graph 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 Prism MCP 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.
Choose MCP Memory Graph 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 | 64/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Freemium | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 157 | 2 |
| Directory activity | 5 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Prism MCP | View MCP Memory Graph |
Tools & capabilities
Prism MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Memory Graph 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.
Prism MCP
{
"mcpServers": {
"dcostenco-prism-mcp": {
"command": "npx",
"args": [
"-y",
"prism-mcp-server"
]
}
}
}
MCP Memory Graph
{
"mcpServers": {
"mcp-memory-graph-2": {
"command": "npx",
"args": [
"-y",
"mcp-memory-graph"
]
}
}
}
Frequently asked questions
Prism MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. MCP Memory Graph belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Prism MCP for knowledge & memory work and MCP Memory Graph 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.
Prism MCP is listed as freemium — a free tier with paid plans. Auth: no auth required. MCP Memory Graph 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 dcostenco-prism-mcp and mcp-memory-graph-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Prism MCP has a quality signal of 64/100 (Good) with 5 views, 0 installs and 157 GitHub stars. MCP Memory Graph has 45/100 (Fair) with 4 views, 0 installs and 2 GitHub stars.