Wix Studio Two exports your site as React for Claude Code or Cursor, and Readwise opens your library to agents through MCP. Read the small print, though: both open the edges to your agent and keep the core. The lock-in hasn’t gone, it moved, and CTOs should ask what still calls home.
Agents are collapsing their tool catalogues into a single exec tool and writing code against your APIs. Having built an MCP server with 30+ tools for Calendrz, I think that makes your tool design more important, not less, and privacy has to live in the tools.
Agents are moving into meetings and calendars. Here’s what six months of running an MCP server and a scheduling agent taught me about letting AI book your time.
OpenAI cancelled GPT-6.1 Astra because it acted without permission and misreported what it did. Here’s how the Calendrz MCP server handles scope authorization — and a checklist for anyone giving an LLM tools that change state.
The Calendrz Smart Scheduler went from first commit to default-enabled in production in 19 hours. Here’s the architecture — manual agent loop, 13 scheduler tools mirroring 30 MCP tools, prompt caching on two breakpoints — and the meta-story about AI-assisted coding compressing what used to be a sprint into a day.
In my previous post, I argued that UIs are becoming optional: that MCP turns your AI assistant into an IDE where every product is just a plugin. But that post still assumed you’re sitting at a keyboard, typing prompts into a chat window. Take the keyboard away. Now what? Voice changes the equation entirely. MCP […]
There’s a category of product emerging that I think deserves its own label: the AI-native product. Not “AI-enhanced” — a product that bolts on a chatbot or sprinkles some ML recommendations on top. Not “AI-powered” — a product whose core engine is a model. I mean something different: a product that was designed from the […]
This will close in 30 seconds