# Model Context Protocol (MCP)

409 Hacker News commenters recommended Model Context Protocol (MCP) and 317 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 1 years (11 owners).

**Verdict:** A widely supported standard for plugging tools and services into AI agents with built-in auth and scoped access, though critics note heavy token use and a rough, unevenly supported spec.

## Why people recommend it

- Broad client adoption, plug-and-play (7 comments): "MCP in its current direction and form is really an OAuth Protocol over http. And it has something other that other agent identity protocols don't: client adoption" ([source](https://news.ycombinator.com/item?id=48331724)) "The whole purpose behind MCP was to provide a low-impedance standard where some set of tools could be plugged into an existing agent with no pre-knowledge" ([source](https://news.ycombinator.com/item?id=45954849)) "There is huge value in having vendors standardize and simplifying their APIs instead of having agent users fix each one individually." ([source](https://news.ycombinator.com/item?id=46211808))
- Restricts and secures agent access (6 comments): "MCP has a great advantage over agent using cli: MCP is much easier to secure so that it's hardwired that the agent can only call the pre-configured MCP server." ([source](https://news.ycombinator.com/item?id=48334669)) "Routing calls through MCPs that only allow specific access lets us keep things secure for servers that don't allow that fine control through the API." ([source](https://news.ycombinator.com/item?id=50132006)) "I've since come back to MCPs, because I want to build my own agents without first having to solve the problem of effectively sandboxing Bash." ([source](https://news.ycombinator.com/item?id=49789420))
- Standardized OAuth and authentication (5 comments): "MCP in its current direction and form is really an OAuth Protocol over http. And it has something other that other agent identity protocols don't: client adoption" ([source](https://news.ycombinator.com/item?id=48331724)) "Authorization, in my opinion, is the big problem you need MCP for, though the current MCP Authorization spec still needs some refinement." ([source](https://news.ycombinator.com/item?id=47216788)) "MCP can be just as badly designed and documented as REST, but at least there's a standard for authenticating and listing the options." ([source](https://news.ycombinator.com/item?id=49565655))
- Easy for non-technical users (4 comments): "our nontechnical employees are now able to answer questions and build interactive data visualizations they would never have been able to do before" ([source](https://news.ycombinator.com/item?id=48963568)) "The big advantage here is that a normal API, direct tool integration or CLI are unpractical to set up for my less technical coworkers." ([source](https://news.ycombinator.com/item?id=49561667)) "MCP can be easily updated with new tools and instructions, and it’s easy to explain how to add to Claude for non-technical people." ([source](https://news.ycombinator.com/item?id=47713317))

## What people warn about

- Consumes lots of tokens, context (5 comments): "Going all-in on Model Context Protocol (MCP) is definitely a bad idea because I noticed the Jira and GitLab MCPs were consuming an excessive amount of tokens." ([source](https://news.ycombinator.com/item?id=49788468)) "I find MCP beneficial too, but do be aware of token usage. With a naive implementation MCP can use significantly more input tokens" ([source](https://news.ycombinator.com/item?id=47659574)) "the main problem I've seen with MCP is that they become a dumping ground and you end up with a ton of context every session" ([source](https://news.ycombinator.com/item?id=49856909))
- Clients support little beyond tools (2 comments): "The biggest disappointment I have with MCP today is that many clients are still half-assed on supporting the functions outside of MCP tools." ([source](https://news.ycombinator.com/item?id=47387264)) "MCP has been mostly relegated to tool calling leaving potentially powerful capabilities on the table due to lac of client support for them." ([source](https://news.ycombinator.com/item?id=49908640))
- Security benefits questioned (4 comments): "how is defining access rights in an application layer the agent has access to more secure than defining the access rights at the target application itself?" ([source](https://news.ycombinator.com/item?id=49796755)) "Relying on an intermediary to provide access controls, and that agents will never access the service directly, seems dangerous and naive." ([source](https://news.ycombinator.com/item?id=49787863)) "Yes, let's have the stohastic parrot guessing machine run executables on the project manager's computer - that can only end well, right?" ([source](https://news.ycombinator.com/item?id=46217727))
- Rough protocol and auth spec (3 comments): "Authorization, in my opinion, is the big problem you need MCP for, though the current MCP Authorization spec still needs some refinement." ([source](https://news.ycombinator.com/item?id=47216788)) "MCP's value isn't in the protocol design (which is admittedly rough). It's in what it enables: persistent, composable integrations that survive across sessions." ([source](https://news.ycombinator.com/item?id=47392873)) "MCP is simply a crappy implementation of this idea because our programming environments do not expose global remote function call mechanisms" ([source](https://news.ycombinator.com/item?id=46552686))

## Cite as

Hacker Approved, "Model Context Protocol (MCP)", https://hackerapproved.com/p/model-context-protocol/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).