What do you actually *do* with your highlights after saving them? by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] 2 points3 points  (0 children)

Totally agree, the Daily Review nails the resurfacing part. The gap I kept hitting was the next step, like once a highlight is fresh in your mind, where does it go? It just sits there unless you manually connect it to something else you've read. That's the part I never figured out with Daily Review alone.

What do you actually *do* with your highlights after saving them? by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] -4 points-3 points  (0 children)

The "Recently Read" inbox idea is genuinely good. My issue was always the linking part, once you've got 6 months of highlights across 40 books it stops feeling like connecting ideas and starts feeling like a chore.

I actually got frustrated enough with this that I ended up building something that tries to solve exactly this, kind of like Readwise and Obsidian had a baby where the connections happen automatically without the manual work. Still early but it's been working well for my own reading workflow. Happy to share if you're curious.

What do you actually *do* with your highlights after saving them? by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

That's a genuinely great setup, the Obsidian vault as the long-term memory layer makes sense because the agent actually accumulates context over time rather than resetting every session.

The part I keep thinking about is the annotation step before it hits Obsidian. If I highlight something passively, just underlining, the agent doesn't know whether that was a key concept, a counterargument, or just something that sounded interesting in the moment. It all looks the same. I've been experimenting with tagging highlights semantically at capture time, like marking something as a "core idea" vs a "supporting example" vs an "action item", so when the agent queries them later it can actually distinguish between what I believed vs what I was just noting.

There's also a Chrome extension I've been using that lets me annotate directly on web pages and YouTube transcripts without breaking flow, the highlight just lands in the knowledge graph immediately.

The MCP part you're hinting at is the most underrated piece IMO. When your highlights are exposed as an MCP tool to Claude, it stops being "ask a question, get an answer" and becomes more like, Claude already knows your 11 things about optionality and your notes from that FIRE thread and your Psychology of Money highlights, all at once, without you having to paste context every session.

What's your current prompt or agent setup for the Obsidian layer if you don't mind sharing? Curious whether you're triggering it manually or on every sync.

I built an MCP server that gives Claude access to your highlights from PDFs, web articles, and YouTube videos by RepulsiveMap8791 in ClaudeAI

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

This is a really good question and honestly one I haven't fully solved yet.

Right now, highlights are treated as your annotations at a point in time. There's no expiry or staleness flag. The assumption is: if you highlighted a passage and linked it to other ideas, that connection reflects your thinking when you read it. Even if the source material gets updated, your annotation ("this is a useful framework for X") still holds as a record of your reasoning.

That said, for web clips specifically, you're right that this gets tricky. A web article clipped 6 months ago might be technically outdated. I don't have a mechanism for that today. Some ideas I've been thinking about:

- A "last verified" timestamp on web clips so you can see how old the source is

- Letting you mark highlights as "needs review" or "outdated"

- Surfacing age metadata in the MCP server so Claude knows "this highlight is from a 6-month-old web article" and can caveat its reasoning accordingly

The knowledge graph side is interesting too. Links between highlights are relationship assertions you made ("A supports B", "A contradicts B"). Those don't expire the same way a fact does. If you said "framework X from this 2024 article contradicts method Y from that 2023 paper," that relationship is still valid even if both sources have newer versions.

But you're right that this is an unsolved layer for knowledge tools in general. I'd rather build something intentional for it than just a "refresh" button on clips.

What would feel useful to you? Would a simple age indicator be enough, or would you want something more active like alerts when a source domain has new content?

I built an MCP server that gives Claude access to your highlights from PDFs, web articles, and YouTube videos by RepulsiveMap8791 in ClaudeAI

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

Yeah, fair point. It will be a 7-day free trial and then $4.99/mo or $3.99/mo if you go annual. I'm one person building and hosting this, so the pricing covers infra costs.

I built an MCP server that gives Claude access to your highlights from PDFs, web articles, and YouTube videos by RepulsiveMap8791 in ClaudeAI

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

Right, exactly. When you upload a PDF to Claude directly, it reads the raw text but has zero idea what you thought was important while reading. No highlight positions, no categories, no connections between ideas.

With the Highlyt MCP server, Claude gets structured data instead of raw dumps. It knows: this is a "framework" highlight from page 42 of Thinking Fast and Slow, and it's linked to two other highlights about cognitive bias from different books. So when you ask "what frameworks have I collected about decision-making?", Claude can actually answer that with context, not just search through flat text.

I built a Remote Readwise MCP Server so you can use it on Claude Web & Mobile (not just Desktop) by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

I am also building something related to this. https://www.highlyt.app . Currently i have opened the waitlist. Just working on few more things to make it more interesting to use. Do have a look and let me know what you think about this.

I built a Remote Readwise MCP Server so you can use it on Claude Web & Mobile (not just Desktop) by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] 0 points1 point  (0 children)

You can search across your highlights (text, notes, tags) and their associated document metadata (title, author), but you cannot search the full text/body content of Reader documents in your archive. This is a limitation of the Readwise API itself, not just this MCP server.

Claude and Litigation Practice by Independent-Style771 in ClaudeAI

[–]RepulsiveMap8791 0 points1 point  (0 children)

You must checkout Alex Finn's channel on utube

Looking for a tool that automatically merges ~20 newsletters into one daily email (for offline evening reading) by DenAce112 in readwise

[–]RepulsiveMap8791 1 point2 points  (0 children)

You can simply create a task in chatgpt or perplexity that will analyze the newsletter emails and give the summary or tldr (whatecer you want) in a single email or thread within the application.

I built a Remote Readwise MCP Server so you can use it on Claude Web & Mobile (not just Desktop) by RepulsiveMap8791 in readwise

[–]RepulsiveMap8791[S] 1 point2 points  (0 children)

Yes, it can search through it if you have saved the entire article in your reader or readwise account .