Opyt vs Claude on its own

Opyt runs inside Claude. The question is not which one, but whether Claude alone can see your sources.

Start with the concession, because it is a large one. You do need Claude, or Cursor, or another client. Opyt is an MCP server with no interface of its own, and it is worthless without one. For anything public and indexed, your assistant's built-in search already finds it and Opyt adds nothing at all.

The problem is that the sources Opyt is built on are not publicly fetchable. Fetching a post on x.com returns HTTP 402 Payment Required; X's robots.txt admits Google and almost nobody else; and an assistant's web fetch makes a plain request that does not log in or fill in forms. Your bookmarks, likes, follows and Substack subscriptions are private to your account by definition, so no crawler will ever reach them, however good it gets.

The second problem outlasts the first. Even where a source is reachable, an assistant that fetches it keeps nothing. The next session starts from zero, re-fetches and re-pays. Nothing accumulates, so there is nothing to count, nothing to compare across months, and no way to ask what you have actually been reading.

At a glance

	Opyt	Claude on its own
Your bookmarks and likes	The seed of the whole store	Private to your account; no crawler reaches them
A post on X	Ingested and kept, in full text	x.com answers a plain fetch with 402
Your Substack subscriptions	Read from your own session, full text	Private, and paywalled posts need your subscription
A person's body of work	A confirmed person can add their discovered sources	Re-crawled per question, where it is reachable at all
What you read last spring	Counted across the whole store by source, kind and author, over any date window	Not retained; every session starts from zero
A public topic you have never touched	Nothing; it is not in the store	Deep research is the right tool
Cost per question	Local keyword ranking; no model call	One fetch-and-read per source, every time
What it is	An MCP server your client calls	The client itself

Where Claude on its own is better

Anything public and indexed. If the answer is on the open web, built-in search finds it and Opyt contributes nothing.
Deep research on a topic you have never followed. Opyt returns nothing there by construction. The store holds only what you already read, and none of it is about a field you never followed. Deep research is included in the plan you already pay for.
Projects and a long context window handle “here are twenty documents, answer this” with no install and no store.
Agentic browsing can drive your logged-in session, so it can reach X. The limit is throughput rather than capability: it renders and reads pages one at a time, on request, and a bookmark backlog or a full author archive is not a browsing session.
Nothing to install. Opyt needs a local install on a Mac (Python, uv and an MCP-client configuration); claude.ai can then read it through the Opyt connector.

Where Opyt is better

It reads what no crawler can: bookmarks, liked authors, follows, and subscriptions that are private to your account. A plain fetch of an x.com post returns HTTP 402 (checked 2026-08-29).
It keeps what it fetched in a local SQLite store. An assistant re-fetches the same page every session that needs it.
Person-level collection. Confirming an author pulls their available discovered sources, and the X pull is free because it reads the X session you signed into once for Opyt.
Retrieval is local BM25 keyword ranking with no model call. An assistant answers by fetching and reading, once per source, every time it is asked.
It is read-only by construction. Agentic browsing drives your live session with the ability to act. Opyt never posts, follows or likes.

Which one

Pick Claude on its own if

The answer is on the public web
You are asking about something you have never followed
You have no saving habit to build on

Pick Opyt if

Your sources sit behind a login you already have
You want the fetch kept, not repeated
You want to ask about your own reading

Opyt is worthless without a client like Claude, so this was never a fork. The narrow question is whether Claude alone can reach your bookmarks, your subscriptions and a person's whole archive. It cannot, and what it does reach, it does not keep.

install Opyt free, MIT, five minutes

Opyt vs Hermes Agent + cronSelf-hosted autonomous agents on a schedule

Opyt vs AI browsersBrowsers with an agent inside your logged-in session

all comparisonsevery category, side by side

useopyt.comwhat Opyt is for

hello@useopyt.comquestions and feedback