| FMRS | 60 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 12 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Development teams using Claude Code, Codex CLI, or other MCP clients that need cross-session memory
- Users who want to self-host SQLite or sync to Cloudflare D1/R2
- Long-term memory use cases that need supersession lineage and deduplication rather than append-only text
- Advanced users willing to configure embedding and LLM providers themselves (OpenAI, OpenRouter, Cloudflare Workers AI, etc.)
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| Not for | - Users who want a zero-configuration setup — embeddings and the LLM require your own keys and endpoints
- One-off question-answering tasks that do not need persistent memory
- Environments that cannot absorb the operational cost of a long-running container or a LaunchAgent-managed proxy
- Users expecting vendor support or an SLA — the project is community-maintained
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| Required permissions | - Local file access: creates and reads/writes a SQLite database file (default ~/.local/share/memora/memories.db) and a cache directory
- Network access: calls the configured embedding endpoint and LLM endpoint (OpenAI, OpenRouter, Cloudflare Workers AI, etc.)
- Cloud storage credentials: AWS_PROFILE and AWS_ENDPOINT_URL for S3/R2 sync, or CLOUDFLARE_API_TOKEN for D1
- Local port binding: the graph server listens on 127.0.0.1:8765 by default; HTTP transport defaults to 127.0.0.1:8000
- Container deployment requires running Apple's container CLI and installing a LaunchAgent-managed local proxy process
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| Risks and side effects | - If the embedding endpoint is misconfigured (for example pointed at OpenRouter), Memora silently falls back to TF-IDF keyword bags unless MEMORA_EMBEDDING_STRICT=1 is set, degrading vector quality while looking healthy
- A wrong store name in MEMORA_DATABASES is undetectable by errors: reads succeed but writes land in another project's store; verify with the database field from memory_stats
- Credentials are injected into the process via environment variables; an over-permissive credential file may be readable by other local accounts (the docs recommend chmod 600)
- Memory content is sent to the configured embedding and LLM providers, which matters for sensitive data
- The container runtime reassigns the container's IP on every start; connecting directly instead of through the proxy produces a permanent silent hang
- LLM deduplication and absorb can merge or supersede memories; lineage is preserved, but wrong judgments still affect retrieval results
- Document fragments are protected by integrity guards, but deleting the whole document deletes every fragment with it
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Code, Codex CLI, Neovim (Telescope) | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 31 | 26 | 11 |
|---|