Oh my god, the USB-C analogy again? [1] Seems like a coordinated spam attack like the way Triplebyte financed endless “hiring is broken” blog posts.
[1] I get USB as a universal interface, but I have a drawer full of USB-C cables that all look alike. It are very different in their capabilities. I am thinking of throwing out all the cheapies and replacing them with $30 cables so I can charge my phone in less than a week.
It’s even worse than that, beyond power delivery and data speed which are at least mentioned in the product listing most of the time (even if they’re lying), USB-C also covers things like usb audio, which is never ever mentioned in the product listing and usually doesn’t work on cables that cost as much as $100. The only cables I’ve found that actually work for everything are Apple cables.
Let's not even talk about alt modes other than audio like display port. really if you want decent cables name brands that support thunderbolt are the only option for somewhat quality - though most still break or get kinked up near the ends. Thunderbolt 3/4 especially the latter specs to 100w power delivery, display port support and should be the minimum cables are built to imo.
that said you can mildly ignore at your own risk cable lengths and get 10 or 15ft cables that can and do charge without any noted impact on speed or charger heat but these too are a crapshoot since no name brand carries these due to them being out of spec (I think 3 and/or 6ft are spec, I forget)
Sorry I couldn't come up with a better analogy - it's popular because it does make a lot of sense! Happy to hear any better ideas when it comes to MCP analogies
Instead of focusing too much on the analogy aspect (which, to be fair, was a very small part of the article), I tried to include lots of project examples so people could get a better idea of what MCP is, and how you can actually use it.
It’s already changed how I work in the last week that I discovered it.
I’ve used the Atlassian MCP to help organize my backlog and consolidate tickets into epics, and to leave comments on tickets based on summaries of commits, and even transition tickets to testing and reassign them.
I’ve used the GitHub MCP to write PR descriptions too.
I think once we start getting hybrid MCP + LSP servers (with debugging support), the editors will get even smarter.
It's just a an RPC-like protocol and SDKs that implement it to help LLMs understand what they can do with other systems (eg GitHub, file systems, Obsidian, etc). It uses a client-server architecture where servers implementing MCP expose a set of commands and prompts to interact with a specific system. And clients (LLMs) can interact with the servers it knows about.
So MCP makes it easy for LLMs to interact with anything. And there are now hundreds of such servers.
MCP beats Cursor & other AI IDEs hands down. If you use Cursor, you’re ahead of the pack but behind the eight ball - both at once. Things are moving!
I’m writing this while supervising Claude desktop as it writes out a backend and frontend for a SaaS tool, all based on a simple concept.
Pasted in 10-ish paragraphs of product design and some rough bullet points about data model, stack, screens, and functionality. Then pressed enter and let it rip.
It’s doing its work by creating directories, running commands (eg “npx create-next-app”) and writing files to the file system.
So far it’s bootstrapped an entire python backend with all the right boilerplate, run create-next-app and filled in a full frontend with dozens of components and every page I asked for. I’m reading every line of code as it’s written. It is surreal watching the app magically appear, file by file, in the vscode sidebar.
Everything it’s doing has been according to best practices as of 2025. In an hour of approving tool usages and typing “Continue” into Claude Desktop, it one-shotted an app that could stand a decent chance at a hackathon.
It didn’t do everything in one shot: I had to ask it to make the test suite and had to ask it to replace mock calls in the frontend with real calls to the backend. It trips over when it generates large files, but happily splits them into smaller ones with the prompt “Continue, but split it into several files”.
Claude makes some really nice choices. This is making me seriously reconsider my 6-week-old Cursor subscription. This was all done using just Claude Desktop on macOS.
It may have some issues, but people are already building some really cool stuff with it - as mentioned in the original article. So I am guessing that's where the hype is coming from.
16 comments
[ 3.3 ms ] story [ 49.1 ms ] thread[1] I get USB as a universal interface, but I have a drawer full of USB-C cables that all look alike. It are very different in their capabilities. I am thinking of throwing out all the cheapies and replacing them with $30 cables so I can charge my phone in less than a week.
that said you can mildly ignore at your own risk cable lengths and get 10 or 15ft cables that can and do charge without any noted impact on speed or charger heat but these too are a crapshoot since no name brand carries these due to them being out of spec (I think 3 and/or 6ft are spec, I forget)
Instead of focusing too much on the analogy aspect (which, to be fair, was a very small part of the article), I tried to include lots of project examples so people could get a better idea of what MCP is, and how you can actually use it.
Appreciate the feedback!
I’ve used the Atlassian MCP to help organize my backlog and consolidate tickets into epics, and to leave comments on tickets based on summaries of commits, and even transition tickets to testing and reassign them.
I’ve used the GitHub MCP to write PR descriptions too.
I think once we start getting hybrid MCP + LSP servers (with debugging support), the editors will get even smarter.
But if it's a structured protocol, how can it be general enough to cover all use cases? (say the syntax of an obscure simulation language)
So MCP makes it easy for LLMs to interact with anything. And there are now hundreds of such servers.
I’m writing this while supervising Claude desktop as it writes out a backend and frontend for a SaaS tool, all based on a simple concept.
Pasted in 10-ish paragraphs of product design and some rough bullet points about data model, stack, screens, and functionality. Then pressed enter and let it rip.
It’s doing its work by creating directories, running commands (eg “npx create-next-app”) and writing files to the file system.
So far it’s bootstrapped an entire python backend with all the right boilerplate, run create-next-app and filled in a full frontend with dozens of components and every page I asked for. I’m reading every line of code as it’s written. It is surreal watching the app magically appear, file by file, in the vscode sidebar.
Everything it’s doing has been according to best practices as of 2025. In an hour of approving tool usages and typing “Continue” into Claude Desktop, it one-shotted an app that could stand a decent chance at a hackathon.
It didn’t do everything in one shot: I had to ask it to make the test suite and had to ask it to replace mock calls in the frontend with real calls to the backend. It trips over when it generates large files, but happily splits them into smaller ones with the prompt “Continue, but split it into several files”.
Claude makes some really nice choices. This is making me seriously reconsider my 6-week-old Cursor subscription. This was all done using just Claude Desktop on macOS.
Got it from this guide: https://www.youtube.com/watch?v=ly3bed99Dy8
- Model Context Protocol on GitHub: https://github.com/modelcontextprotocol - Docs: https://modelcontextprotocol.io/introduction - Matt Pocock MCP Tutorial: https://www.aihero.dev/model-context-protocol-tutorial - Block's Head of Dev Rel's take on Agentic AI and the MCP Ecosystem (and a bunch of other articles): https://block.github.io/goose/blog/2025/02/17/agentic-ai-mcp...