Full recording of this week's State Change Mastermind livestream with Ray Deck and Dimitris Goudis. We talked about MCP connectors as the new interface for applications, turning experts' videos into knowledge-graph MCPs, and controlling a Mac from the Claude app. 00:00 Intro 01:11 Dimitris: MCP connectors are the new user interface (ClickUp to Airtable in one prompt) 02:52 Expert knowledge bases as public MCP connectors (Caleb Ralston, Rory Sutherland) 05:23 Live demo: adding the Rory Sutherland connector in Claude and asking it how to promote the livestream 16:33 How it was built: 3-4 hours, the MCP shaped around the database 19:34 Robert: notes from the MCP Dev Summit in Toronto (auth, governance, stateless and async) 22:35 Live demo: controlling my Mac from the Claude app by voice through the Snappy OS connector 28:33 How notifications get back to you (MCP tasks, the Claude app) 32:27 Does it only work on a Mac? 34:55 Experts and machines as connectors, and bespoke vs off-the-shelf MCPs 38:11 Getting things done vs gold-plating auth 41:00 Dimitris: lessons from designing the ontology for a custom knowledge graph 46:46 Wrap-up

Libretto is an open-source CLI that lets agents turn website workflows into fast, reusable scripts you can deploy! Check it out here: https://libretto.sh/ -- I think this would be very useful for anyone (like me) who is exploring new ways in getting more control over browser automation with AI!

er, seems like Claude got a new habit recently...

Thanks to a great idea from Ray Deck, I have reduced the number of tools in the snappy.ai Xano MCP from ~180 tools and ~150,000 tokens to ~1000 tokens and 3 core tools: 1. Gemini Flash Powered Search - "What tools do I have?" (Semantic search across all tools - e.g., "create table", "list functions") 2. Info - "Tell me more about that specific tool" (returns parameters, examples, docs) 3. Execute - "Do it" (runs the tool with the right parameters) Now the initial handshake costs only ~1000 tokens instead of 150,000. Claude discovers tools as needed rather than loading everything upfront. This pattern should work for any MCP with dozens or hundreds of tools. Instead of exposing everything at once, create a search/discovery layer that lets Claude Code find what it needs when it needs it!

Spent about 10 minutes on requirements and planning with Claude Code, kicked off the plan, took a shower, and came back to this... nice. (Snappy-Xano or V2 used on this one)