Memory (MCP reference server) vs Tokenrip

Memory (MCP reference server)

Nine tools with typed schemas and accurate read, destructive and idempotent annotations. No pagination or limits. read_graph returns everything and search_nodes every match.

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.

Memory (MCP reference server)

1. Set MEMORY_FILE_PATH to an absolute path. The default sits inside the npx cache
2. Use search_nodes or open_nodes instead of read_graph once the graph has more than a few hundred entities
3. Make memory writes one at a time. Parallel calls in one turn can overwrite each other in 2026.8.31
4. Create both entities before create_relations. A missing endpoint fails the whole batch
5. Keep observations short and factual. They come back verbatim in every later read

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.