Indeed. The biggest waste might be the overuse of MCP for everything. Sure it makes the initial development easier but then for every connection you're using a hundred billion dollar parameter model to decide how to make the call when it's usually completely unnecessary and then prone to random errors. MCP is the hammer that can make literally everything look like a nail...

▲

senordevnyc 8 hours ago | parent [-]

I see this ranting against MCP all the time, and I don't get it, maybe I'm missing something. I'm currently using an MCP in Cursor to give agents read-only access to my staging and prod databases, as well as BugSnag's MCP so it can look up errors that happen in those environments. It works great. What should I be using for this if not MCP?

▲

visarga 7 hours ago | parent | next [-]

Make a CLI tool for it, of course

▲

senordevnyc 2 hours ago | parent [-]

What? Why? What advantage does that have over just using an MCP server that exposes tools to run queries?

	▲	nojito 28 minutes ago \| parent [-]
		Context. Why would I use an MCP when I can use a cli tool that the model likely trained on how to use?

▲

canadiantim 6 hours ago | parent | prev [-]

agent skills, or use claude code to iteratively condense an MCP you want to use into only its most essential tools for your workflow

	▲	senordevnyc 2 hours ago \| parent [-]
		Agent skills are just a markdown file, what’s in that markdown file in your scenario? And the MCP already only has the most essential tools for my workflow: the ability to run queries against a few databases.