In case you haven't seen it, the MCP repo actually has Puppeteer as one of their example servers: https://github.com/modelcontextprotocol/servers/tree/2025.3....
As for authentication most are locally run, or run on generic data like running a nodejs server mcp would be used locally by a team not exposed on the internet so access restrictions arent really needed
It has been possibly the most fun I've ever had programming, as it's been unbelievably effective and quick. I believe the hype. I'll note I'm also very wary of the potential of malicious MCP servers and am rather hesitant to use any "community" projects, as much as it saddens me to feel I'm losing my trust in the open source community.
It's fine for a library conversion project but I won't be surprised this is how things are headed in real production software too
As simple as MCP conceptually can be, nothing like that was this simple and efficient before MCPs. It's a truly game-changer.
Disclaimer: I’ve worked on this project.
'Vibe coding' has been great for us to prototype quickly, launch and test. As we kept building the complexity grew so much that we are hitting debugging death loops. Thats when we built this MCP.
My perspective is that MCPs are like browser extensions. There is nonpoint in building another IDE from scratch. IDEs like Cursor unlocked massive distribution channel and MCPs are hreat way to solve specific problems.
As you rightly observed, it's not the tech that is interesting. It's the ability of the tech to meet where users are is what makes it great. From my point of view, there is a specific context in which people vibe code - hobby projects, indie projects to make money, projects on legacy code, etc. They either might not have time or skill to do even simple things like adding an API. And thats where MCPs flourish. And as to why MCPs are making to the top, I think its because there are many of us who are matching the persona I mentioned.
The value is that this interface is the other end of a socket; implement it, and your LLMs will have magic tools. Sure it’s just another JSON-RPC adapter, but it’s a JSON-RPC adapter that works and has working integrations.
Give it a try, if you remain open minded to the potential I suspect you can find a use case and application that would shock you in its efficacy.
You insinuating that Anthropic is using bot rings to promote MCP is not only nonsense, it's also breaking the HN guidelines.
From what I could find online, it just works in Claude desktop app and there are some online efforts for mcp clients, but even ollama maintainers are confused about the implementation (https://github.com/ollama/ollama/issues/7865)
I agree with you, I also saw quite a few MCP posts on Show HN recently.
I didn't understand what the whole MCP thing was about, so my buddy and I hacked on this idea out of curiosity.
I almost didn't post it on Show HN, I thought "Ah no, nobody cares. It'll just disappear among the other posts".
Woke up Sunday morning, discovered the post is on the homepage of HN.
Re JSON-RPC, I don't have a lot to add to the conversation. I'll look into the MCP JSON-RPC spec though!
It’s incredibly exciting. I started using the Atlassian MCP to get Claude to help me clean up our tickets.
Do things like “can you find all the tickets related to profile editing and combine them into an epic?”
That's a great use case. I imagine that makes you more productive because you can get multiple related issues out of the way by spending time in the same corner of your code base.
What other MCPs or use cases have caught your attention ?
I’ve had it update my tickets (like, leave a comment summarizing the code changes, transition the ticket.)
And I’ve described our workflow in a cursor rules file. And it knows to reassign the ticket to a certain person when I ask it to mark something ready for test. Or if I want to transition to a workflow strep 3 steps down, it knows my workflow from the rules file ands can perform each transition in sequence.
MCP itself just seems to be JSON-RPC with a schema to be self-describing, so it's not really that interesting that it warrants one post per day. The web page touts it as the magic needed to ensure you don't have to write API adapters for your LLM uses. Well, except you need to write or use an MCP server to do the translation. So unless you're using one that already exists (though hundreds have been advertised on HN recently,) you're just shifting the problem by adding a layer of indirection.
They also specifically say that authentication is something we'll work out later, so it seems none of these will have access to the data that actually has value.
I have no idea about this account specifically, but I'm starting to suspect there's a bot ring somewhere.