✳flâneur — a map of the web's best reading

MCP is not good, yet.

cra.mr · 909 words · saved by 1 readers

Something’s been bothering me lately surrounding the conversation of MCP servers. Everyone, seemingly, is talking about how MCPs are great, and we should be building MCPs, and adopting MCPs, and rethinking UIs with MCPs, becoming best friends with MCPs, getting married to MCPs, you know, the works. Except they’re not good. Not yet. If you’ve somehow been living in a cave and don’t know what the acronym of the month stands for, MCP is short for Model Context Protocol. Its a specification started over at Anthropic, designed to create a pluggable architecture for a bunch of concerns we see in things like Agents. One of its most simple value props: it lets you plug in tools to any agent (e.g. Cursor, Claude, etc), as long as they support the protocol. Hypothetically super powerful. It started as a local server that operated primarily through stdio (standard input, as in piping to a unix socket). A bunch of rapid fire prototypes were built, mostly requiring you to wire up an access token fr

MCP is not good, yet. Something’s been bothering me lately surrounding the conversation of MCP servers. Everyone, seemingly, is talking about how MCPs are great, and we should be building MCPs, and adopting MCPs, and rethinking UIs with MCPs, becoming best friends with MCPs, getting married to MCPs, you know, the works. Except they’re not good. Not yet. If you’ve somehow been living in a cave and don’t know what the acronym of the month stands for, MCP is short for Model Context Protocol . Its a specification started over at Anthropic, designed to create a pluggable architecture for a bunch of

Explore this link on the map →

related reading