You could even repurpose the MCP so you only ever produce the API documentation as EVERY response. No LLM necessary.
You could even repurpose the MCP so you only ever produce the API documentation as EVERY response. No LLM necessary.
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.
You've reached the end!
jwally•2h ago
Antolius•2h ago
But yeah, a lot of it (including tools) maps well to HTTP semantics. In fact, at work we implement our features as HTTP APIs, and we’ve built a framework that exposes them as MCP servers.