3 ms·
MCP is great for when you’re integrating tools locally into IDEs and such. It’s a terrible standard for building more robust applications with multi-user suppor
by gsibble 1y ago
MCP is great for when you’re integrating tools locally into IDEs and such. It’s a terrible standard for building more robust applications with multi-user support. Security and authentication are completely lacking.
99% of people wouldn’t be able to find the API keys you need to feed into most MCP servers.
- pkoird 1y agoWhat, according to you, are some alternatives that exist or are in development that fill these gaps?
- bswamina 1y agoYou are correct ... it is still early days IMHO ... will have to see how this evolves
- lianlianlian 1y ago[dead]
- sunpazed 1y agoWhile I’m a fan, we’re not using MCP for any production workloads for these very reasons. Authentication, session management, etc, should be handled outside of the standard, and outside of the LLM flow entirely. I recently mused on these here; https://github.com/sunpazed/agent-mcp/blob/master/mcp-what-is-it.md https://github.com/sunpazed/agent-mcp/blob/master/mcp-what-i...