Re:MCP vs. API Explained
by ImPostingOnHN on Sunday March 09, 2025 @11:11AM
(#43309709)
It sounds like pushing the logic of API calling into one of the many "mcp servers", with the user still needing to go through the manual step of creating accounts on third party services, generating a bunch of different tokens, and dealing with them all.
In essence it seems like an additional shim that removes all the security of API tokens while still leaving the user to deal with them.
Side note, has Tron taught us nothing about avoiding AI MCPs?
Re:MCP vs. API Explained
by phillipcarter on Sunday March 09, 2025 @12:18PM
(#43310545)
Yes, although this is not a consumer play. This is an enterprise play. At my workplace, I'm already signed in to my document portal, debugging tools, slack, and other tools for my work through Okta SSO. I imagine some future agent I use to sift through various things will have similar access privileges.
MCP standardizes how LLMs can call tools at runtime, and how tools can call LLMs at runtime. It's great!