MCP stopped being a protocol experiment this week and started behaving like infrastructure. Three things happened at once.

We shipped mcp.hosting - one config, every MCP server, synced to every client. Free for up to three servers. It exists because managing MCP servers across Claude Code, Claude Desktop, Cursor, and VS Code separately is the kind of friction a protocol only hits once it's past the experiment phase.

We also open-sourced tailscale-mcp: 99 tools, 4 resources, 727 unit tests, full Tailscale v2 API coverage. Agents can compose multi-endpoint tailnet workflows in one turn - no script, no glue code.

Meanwhile, Anthropic redesigned Claude Code around parallel sessions, shipped Routines (scheduled jobs that run on their infra, not your laptop), and added an xhigh effort level for Opus 4.7. OpenAI shipped a Codex that clicks and types on your desktop - clearly chasing Claude's computer-use playbook.

And MCP got its first "by design" security fight: Ox Security published a supply-chain flaw report, Anthropic declined to change the protocol, sanitization is the developer's problem. That fight is going to repeat - and probably soon - because the attack surface lives in the hosting and client layers, not in the protocol itself.


From us

From the Yaw blog

Claude Code this week

The broader week

That's the week. See you Sunday.