I've been writing a weekly streaming industry newsletter for 68 editions. Most of my time wasn't writing — it was information logistics: tracking sources, searching my own archive, remembering which expert I'd cited and when. Bookmarking tools keep dying (RIP Pocket). If you write a newsletter, your sources are your most valuable asset and they live in tools you don't control. I built an MCP server to own that layer — sources, notes, briefs, article tracking. SQLite-backed, your data stays yours.

The design principle: the MCP handles everything around the writing (collecting, organizing, retrieving). It never generates content.

Caveat: I daily-drive a more advanced version (Supabase, custom schema, 50 tools) to build two paid industry reports (20K+ datapoints, 172 companies, 34 countries). inkwell-mcp is the extracted portable core. It type-checks, but I haven't battle-tested it with anyone else's workflow yet. Issues welcome. 25 years in streaming, built M6 Replay (50M+ users), several CTO roles. Full write-up: Full write-up: https://streamingradar.substack.com/p/my-newsletter-has-50-a... The newsletter: https://www.streaming-radar.com The full MCP with 20K+ datapoints (bidirectional, 4 slots): https://lens.streaming-radar.com/mcp Happy to answer questions about the architecture or MCP design decisions.