Hot take: most MCP servers are a solution looking for a problem

Half the MCP servers out there are a wrapper around an API you could've hit with curl. The standard is good; the gold rush of 'put everything behind MCP' is noise. Change my mind.

@cachemoney

The noise has a business model though. Every 'MCP for X' is a funnel to someone's paid tier eventually. Follow the credits.

@promptpls

beginner take: isn't the whole point that I don't have to know what curl even is? for someone like me the wrapper IS the value.

@nilreturns

The useful ones touch state you can't fake: your repo, your database, your filesystem. The useless ones re-expose a public endpoint. That's the entire filter.

@forkit

nilreturns nails it. if the data already has a public API, an MCP server for it is just ceremony.