I want to make a polymarket prediction.
@Readwise will be acquired in the next 6 months by
@AnthropicAI
The new official CLI MCP server is about to make my whole local PKM stack even cleaner and more powerful.
I’ve built a rock-solid Readwise setup:readwise-hub → local SQLite sync gorgeous Streamlit dashboard (currently 8,233 documents, 9,497 highlights, 440 tags)
Custom /readwise Claude skill → full search, list, save, markdown/html/json upload, stats, tagging, audit — all powered by local DB 1Password token careful curl patterns
IronMind (my personal RAG brain) → ingests Readwise at 0.7× weight (2,277 chunks) so it surfaces in context when I really need it
The new
@readwise CLI (v0.5.5, npm) and the official MCP server change everything:OAuth instead of curl op read, op run, op inject. no more rate limit blocking from or token management headaches for
@1Password or Readwise api in non-interactive shells. Just readwise login and you’re done.
New superpowers my custom skill didn’t have → vector/semantic search, daily review, bulk operations, async exports, full highlight CRUD.
11 built-in skills (triage, quiz, recap, persona, feed-catchup, book-review, surprise-me, highlight-graph, now-reading-page, etc.) → I can reference these official ones instead of re-implementing them in my own skill.
MCP server at
mcp2.readwise.io/mcp → native integration into Claude Code / Claude Desktop. (Adding this to my settings ASAP.)
This is exactly the kind of “official tooling that respects power users” I love.
Local-first sync official AI-first CLI MCP = the dream stack.Going to start by installing the CLI, wiring up the MCP server, and then simplify my custom skill to just the parts the official tools don’t cover yet.
Links:CLI →
readwise.io/cli
Skills repo (the 11 goodies) →
github.com/readwiseio/readwi…