The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

Simon WillisonVoices

MCP was always a bad idea?

September 20

My comment on MCP was always a bad idea? — Hacker News. This article entirely misses the value that MCP brings today.

MCP, skills & tools hacker-news model-context-protocol

Read at Simon Willison ↗

One letter a week, in your inbox.

Latest

MCP was always a bad idea?

Related

GitHubPresentation: Context Engineering at LinkedIn: How We Built an Organizational Context Layer for AI Agents with MCP InfoQ AI

GitHubManage the code coverage ruleset condition with the REST API GitHub Changelog

ToolsWebMCP support now available in mcp-handler Vercel Blog

GitHubShould you read the code, is RAG dead, and did Skills kill MCP? GitHub Blog

ToolsSub-second artifact deployments are now supported in Vercel CLI Vercel Blog

ToolsThe skills CLI now supports Notion hosted skills Vercel Blog