Hacker News Reader

It's why I asked the question. Maybe I missed something.

MCP is an API. The biggest difference is that it defines some primitives that AI clients know how to implement beforehand so every MCP server works similarly, otherwise each API implements its own way to list the tools available, change/react to changes, authorization, session management, etc. MCP *is* an API.

I'm thinking more as a provider. Why put a model on my side to handle permissions/scope/auth/actions when thats already handled (or easy enough to spin up)by a rest-inspired http api?

If you're needing to give the model direct and broad access to your SqlServer instance...I don't get it.

Dedicated customer facing API is like whitelisting approved actions; MCP feels like getting an LLM to enforce a complex blacklist.

Check WebMCP that ChatGPT Desktop just implemented for a good example.

Now every website can create tools that gpt can use. So it's possible to have your users use AI without the need to pay for tokens.

Reply on news.ycombinator.com