Hey PH — I'm Ludovic, I've been writing Streaming Radar (a French OTT/streaming industry newsletter) for 68 editions. I built the MCP because I was losing 3 hours per edition to information logistics: browser tabs, forgotten Notion databases, and a memory that's confidently wrong about everything. The full Streaming Radar MCP has 50 tools connected to a Supabase database with 20,000+ datapoints. inkwell-mcp is the extracted core — sources, notes, briefs, article tracking. SQLite, zero config, works with Claude Desktop or claude.ai. It's early. The README says "expect breaking changes" and I mean it. Happy to answer questions about MCP, newsletter workflows, or why anyone would build 50 tools for a newsletter. Full write-up on the why and how: [lien Substack Ludo Tries Things] GitHub: https://github.com/ludobos/inkwe... The full Streaming Radar MCP (20K+ datapoints, bidirectional): https://lens.streaming-radar.com...

inkwell-mcp

Open-source MCP server that gives your newsletter a brain

Open-source MCP server that gives your newsletter a brain