Cellarion vs Memory
A side-by-side look at the Cellarion and Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cellarion for other tools and integrations work over a hosted endpoint; choose Memory for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cellarion when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
JWT_SECRET, MEILI_MASTER_KEY.
Choose Memory when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MEMORY_FILE_PATH. - You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 44/100 · Fair | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | JWT_SECRETMEILI_MASTER_KEY | MEMORY_FILE_PATH |
| Verified owner | Community listing | Verified |
| GitHub stars | 26 | 91,512 |
| Directory activity | 2 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Cellarion | View Memory |
Tools & capabilities
Cellarion tools
No tool names declared yet. Check the project README from the listing page.
Memory tools 9
create_entitiesCreate multiple new entities in the knowledge graph. An entity whose name already exists, or repeats an earlier entity in the same call, is skipped and its observations are not added; the result lists the skipped names in `skipped`. Use add_observations to add observations to an existing entity.create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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.
Cellarion
{
"mcpServers": {
"cellarion": {
"url": "https://cellarion.app/api/mcp"
}
}
}
Memory
{
"mcpServers": {
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
],
"env": {
"MEMORY_FILE_PATH": "YOUR_MEMORY_FILE_PATH_HERE"
}
}
}
}
Frequently asked questions
Cellarion is categorized under Other Tools and Integrations and uses a remote HTTP/SSE transport. Memory belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Cellarion for other tools and integrations work and Memory for other tools and integrations.
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.
Cellarion has no declared pricing — check the project's own site. Memory 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 cellarion and memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cellarion has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 26 GitHub stars. Memory has 89/100 (Excellent) with 8 views, 0 installs and 91,512 GitHub stars.