Hacker News new | past | comments | ask | show | jobs | submit
cheema33 | on: Chrome DevTools MCP (2025)
> Also MCP is very obviously dead

Some people will push back on this. They are holding out hope that the recent improvements Anthropic has made in this regard have improved the context rot problem with MCP. Anthropic's changes improve things a little. But it is akin to putting lipstick on a pig. It helps, but not much.

The reason MCP is dying/dead is because MCP servers, once configured, bloat up context even when they are not being used. Why would anybody want that?

Use agent skills. And say goodbye to MCP. We need to move on from MCP.

maxwellg | parent | next
Is your agent harness dropping the entire MCP server tool description output directly into the context window? Is your agent harness always addig MCP servers to the context even when they are not being used?

MCP is a wire format protocol between clients and servers. What ends up inside the context window is the agent builder's decision.

ktoo_ | parent | next
> it is akin to putting lipstick on a pig. It helps, but not much.

The lipstick helps? This had me in stitches. Sorry for the non-additive reply. This is the funniest way I have seen this or any other phrase explained. By far. Honestly has made my day and set me up for the whole week.

dominotw | parent | next
i am using notion mcp. is there a corresponding skill. also wtf is a plugin.
Rapzid | parent
The bloat problem is already out dated though. People are having the LLM pick the MCP servers it needs for a particular task up front, or picking them out-of-band, so the full list doesn't exist in the context every call.