| ▲ | whalesalad 8 days ago | |
MCP sucks because it has to be connected to a desktop client. I'd love to build some MCP-like integrations but no one on my team can use them. We use LLM's via - as you noted - other means like via Notion, via web UI, via our own API integrations. Until there is a more central way to connect these things - yeah they won't reach mass adoption. | ||
| ▲ | dragonwriter 8 days ago | parent | next [-] | |
> MCP sucks because it has to be connected to a desktop client. No, it doesn't need to be connected to a desktop client. It is true that the original use was for connecting local tools over stdio to a desktop client, and it is currently more supported in desktop clients than others, but it now includes remote support and, e.g., ChatGPT Deep Research has support for remote MCP, but only for servers with a very specific shape. | ||
| ▲ | prpl 8 days ago | parent | prev | next [-] | |
A comprehensive solution for 1. A user interacting with multiple MCP servers, behind a gateway (with MCP client support) to get authentication from the user to those servers in some way (OAuth/OIDC, with PKCE, usually, sometimes token exchange), allowing out-of-band auth 2. The same, but built on identity for service accounts/native identity or something, for automation would enable this. There’s a few SEPs open now around this. | ||
| ▲ | pjmlp 8 days ago | parent | prev [-] | |
No it doesn't, there are ongoing efforts to orchestrate MCPs just like any other kind of Web API. | ||