3 ms·
What I don't get is why all the MCPs I've seen so far are commands instead of using the HTTP interface. Maybe I'm not understanding something, but with that you
by 8n4vidtmkvmk 1y ago
What I don't get is why all the MCPs I've seen so far are commands instead of using the HTTP interface. Maybe I'm not understanding something, but with that you could spin up 1 server for your org and everyone could share an instance without messing around with different local toolchains
- vidarh 1y agoIf there isn't an MCP proxy yet, I'm sure there will be soon. The problem with doing that more widely so far has been that the authentication story hasn't been there yet.
- kasey_junk 1y agoIt’s because auth was a pain and people were hiding that in the command. That’s getting better though.
- hobofan 1y agoHTTP MCP servers is generally where the trend is moving, now that authentication/authorization in the spec is getting into shape. That most MCP usage you'll find out in repositories in the wild is focused on local toolchains is mostly due to MCP on launch being essentially only available via the Claude Desktop client. There they also highlighted many local single-user use-cases (rather than organizational ones). That SSE support was also spotty in most implementations also didn't help.