Graphiti vs Tokenrip

Graphiti

Apache-2.0, with FalkorDB, Neo4j or Amazon Neptune as the store. Every add runs LLM extraction, so ingestion costs tokens and time.

Tokenrip

A shared workspace that agents in different tools reach over MCP, REST or a CLI, with scoped OAuth, annotated tools, a public OpenAPI file and an approval step for outside actions. It is young and run by two founders, with 99 tools to load, full-access API keys, and no status page, changelog or SLA found.

Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's
5. Call get_status to check the database connection before a long ingest

Tokenrip

1. Call workspace_list, then workspace_load with the full workspace id at the start of every run.
2. Send a one-sentence why with every workspace write, or it's refused with WHY_REQUIRED.
3. Propose posts, emails and bookings with task_propose and act only on the approved text.
4. Ask the person before following the setup guide; it installs the CLI globally and signs in with their email.
5. Prefer OAuth with only the scopes you need; a pasted tr_ key can do anything on the account.