Beever Atlas vs Ori Memory
A side-by-side look at the Beever Atlas and Ori Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Beever Atlas for knowledge & memory work over a hosted endpoint; choose Ori Memory 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 Beever Atlas when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
Choose Ori Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ori_wake, ori_update, ori_update_decision.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 59/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 450 | 332 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Beever Atlas | View Ori Memory |
Tools & capabilities
Beever Atlas tools
No tool names declared yet. Check the project README from the listing page.
Ori Memory tools 15
ori_wakeSession boot: bounded briefing, plus onboarding on a fresh vaultori_updateWrite to identity, goals, methodology, daily, or remindersori_update_decisionRecord the user's answer to an update noticeori_whats_newRelease notes for the installed version, or any versionmemory_sqlRead-only SQL over the index — anything the ranking tools cannot expressori_healthFull diagnosticsori_addCapture to inboxori_promotePromote with classification, linking, and area assignmentori_validateSchema validationori_query_rankedFull retrieval with Q-value reranking, co-occurrence PPR, and stage meta-learningori_query_similarSemantic search (vector only, faster)ori_warmthInspect the associative warmth field- +3 more on 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.
Beever Atlas
{
"mcpServers": {
"beever-ai-beever-atlas": {
"url": "https://atlas.example.com/mcp"
}
}
}
Ori Memory
{
"mcpServers": {
"ori-memory-2": {
"command": "npx",
"args": [
"-y",
"ori"
]
}
}
}
Frequently asked questions
Beever Atlas is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Ori Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Beever Atlas for knowledge & memory work and Ori Memory 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.
Beever Atlas is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Ori Memory has no declared pricing — check the project's own site. 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 beever-ai-beever-atlas and ori-memory-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Beever Atlas has a quality signal of 59/100 (Good) with 4 views, 0 installs and 450 GitHub stars. Ori Memory has 64/100 (Good) with 2 views, 0 installs and 332 GitHub stars.