> you can't just use skills and cli tools without a gigantic amount of retooling and increased operational and security complexity

You're describing MCP. After all, MCP is just reinventing the OpenAPI wheel. You can just have a self-documenting REST API using OpenAPI. Put the spec in your context and your model knows how to use it. You can have all the RBAC and rate limiting and auth you want. Heck, you could even build all that complexity into a CLI tool if you want. MCP the protocol doesn't actually enable anything. And implementing an MCP server is exactly as complex as using any other established protocol if you're using all those features anyway

▲

whattheheckheck 6 hours ago | parent [-]

The clients for mcp can drop a url and http in the mcp.json and get access to the application. Can the client do that for every rest api?

	▲	bloppe 6 hours ago \| parent [-]
		Ya, if you just use OpenAPI. That's why I'm saying MCP adds nothing. It's just another standard for documenting APIs. There are many that have been around for a long time and that are better integrated with existing ecosystems. There's also gRPC reflection. I'm sure there are others. LLMs can use them all equally effectively.