Opyt vs Supermemory
This is the closest product on the site, so start with the overlap. Supermemory Personal is free, MIT-licensed and an MCP server, the same shape as Opyt. Supermemory Local self-hosts with one command and runs fully offline against Ollama. Retrieval is hybrid vector and keyword search. And it reaches clients Opyt does not: npx supermemory connect puts one memory in ChatGPT, Claude, Cursor, Windsurf, Perplexity, Gemini and Copilot, where Opyt is a local stdio server you install per client.
The two differ in one place, and it is not retrieval. It is what fills the store. The published connector list is Google Drive, Gmail, Notion, OneDrive, GitHub, Granola and a Web Crawler (supermemory.ai/docs/connectors, checked 2026-08-30). Every one of those is an account you already own or a folder you already keep, and none of them reads a social account. Everything else arrives because you sent it: a URL, a file, a note, a conversation. In fairness to a reader who remembers otherwise: the project began in 2024 as a bookmark app whose Chrome extension imported X bookmarks, and that path is not in today’s connector documentation.
The one rail that could reach the open web is the Web Crawler, and two facts bound it. Their docs describe it as crawling “with robots.txt compliance”, and x.com’s robots.txt answers Disallow: / to every agent except Googlebot, Bingbot and facebookexternalhit (fetched 2026-08-30). It is also a Scale-tier connector at $399/mo, so it is not in the personal product at all. Opyt takes the other route and reads the session your browser is already logged into, which is the only way to a bookmark list.
At a glance
| Opyt | Supermemory | |
|---|---|---|
| What fills it | Bookmarks, likes, follows and subscriptions, read from your own logged-in session | Seven connectors (Drive, Gmail, Notion, OneDrive, GitHub, Granola, Web Crawler), plus what you send it |
| Whose work it holds | Other people’s published work, with a live source URL on every hit | Yours: files, mail, notes, and “deep user profiles from behavior” |
| A post on X | Ingested in full text from your own session | The crawler obeys robots.txt; x.com admits Googlebot, Bingbot and facebookexternalhit, nobody else |
| Unit of ingestion | A person: one confirmation pulls 3,412 posts, 38 repos and 96 essays | An item: one URL, one file, one note |
| Which clients | Any MCP client you install it in, over local stdio | ChatGPT, Claude, Cursor, Windsurf, Perplexity, Gemini, Copilot |
| Personal price | Free, MIT, one API key you hold | Free tier with about $5/mo of usage built in; Pro $19/mo adds the first connectors |
| Counting the corpus | aggregate tabulates 2,830 documents by topic, author and month | Hybrid vector and keyword search, under 300 ms |
Where Supermemory is better
npx supermemory connect takes about thirty seconds, and the same memory then appears in ChatGPT, Claude, Cursor, Windsurf, Perplexity, Gemini and Copilot. Opyt needs Python 3.10+, a clone, a virtualenv and an API key, and reaches only the MCP clients you install it into.Where Opyt is better
add_oracle confirmation pulls 3,412 posts, 38 repos and 96 essays in a single action. Sending a URL stores one document, and a reading habit is thousands of documents wide.frontier re-asks standing queries and stages what is new, deliberately re-reading a six-hour overlap behind its cursor because dedup absorbs it. A four-hour connector sync re-reads accounts you already connected; nothing on that list finds a source you have not.Which one
Nothing here is exclusive. Both are MCP servers, and Supermemory for what you told your assistant alongside Opyt for what the people you trust published is a coherent setup. The line between them is the connector list: everything on Supermemory’s is an account you already own, and Opyt exists for the sources no connector will ever hold.
install Opyt free, MIT, five minutes