Celiums Memory vs Penfield MCP
A side-by-side look at the Celiums Memory and Penfield MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Celiums Memory for knowledge & memory work as a local process; choose Penfield MCP 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 Celiums Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SQLITE_PATH, DATABASE_URL, QDRANT_URL, VALKEY_URL, CELIUMS_API_KEY, PORT, CELIUMS_LLM_API_KEY, CELIUMS_LLM_BASE_URL.
Choose Penfield MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 56/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | SQLITE_PATHDATABASE_URLQDRANT_URLVALKEY_URLCELIUMS_API_KEYPORTCELIUMS_LLM_API_KEYCELIUMS_LLM_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 6 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Celiums Memory | View Penfield MCP |
Tools & capabilities
Celiums Memory tools
No tool names declared yet. Check the project README from the listing page.
Penfield MCP 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.
Celiums Memory
{
"mcpServers": {
"celiums-celiums-memory": {
"command": "npx",
"args": [
"-y",
"@celiums/memory"
],
"env": {
"SQLITE_PATH": "YOUR_SQLITE_PATH_HERE",
"DATABASE_URL": "YOUR_DATABASE_URL_HERE",
"QDRANT_URL": "YOUR_QDRANT_URL_HERE",
"VALKEY_URL": "YOUR_VALKEY_URL_HERE",
"CELIUMS_API_KEY": "YOUR_CELIUMS_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE",
"CELIUMS_LLM_API_KEY": "YOUR_CELIUMS_LLM_API_KEY_HERE",
"CELIUMS_LLM_BASE_URL": "YOUR_CELIUMS_LLM_BASE_URL_HERE"
}
}
}
}
Penfield MCP
{
"mcpServers": {
"penfieldlabs-penfield-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Frequently asked questions
Celiums Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Penfield MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Celiums Memory for knowledge & memory work and Penfield MCP 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.
Celiums Memory is listed as free. Auth: api key required. Penfield MCP is listed as free. Auth: oauth 2.0. 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 celiums-celiums-memory and penfieldlabs-penfield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Celiums Memory has a quality signal of 56/100 (Good) with 3 views, 0 installs and 23 GitHub stars. Penfield MCP has 49/100 (Fair) with 4 views, 0 installs and 6 GitHub stars.