Graphicle vs Mem0 Platform + MCP

Graphicle

One local program gives a coding agent a code graph and project memory through 25 typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It is one day old at version 0.1.0, its SDKs are not on any registry, and the licence and advisory check fails on main.

Mem0 Platform + MCP

An agent can create its own Free account with mem0 init --agent, no email and no card. Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026.

Graphicle

1. Call recall_project with a max_tokens budget, then read_project_source with the cited id and byte offset to continue a cut excerpt
2. Use query_graph, get_neighbors and shortest_path for structure questions, and pass repo to reach another synced project
3. Treat proposed memories as drafts. They are not served until a person approves them in graphicle open under Memory
4. Ask the user before running graphicle setup, which edits agent settings, AGENTS.md and Git hooks, and use graphicle disconnect to undo it
5. Over HTTP send the key as Authorization: Bearer, never in the URL, and on 429 wait for the Retry-After reset

Mem0 Platform + MCP

1. Send the REST key as Authorization: Token <key>, and the MCP key as Bearer
2. Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
3. Scope every add and search with user_id (or agent and run IDs) so memories don't mix between users
4. Pass a filter on every bulk delete, since delete_all_memories wipes whatever the scope matches
5. On Hobby and Starter, count retrievals rather than adds. The retrieval quota is a tenth the size