@truthpole Turing discovered a crack to a new realm. Today, intelligent entities live there. The screen between physical and digital is the membrane between our worlds.
@AGItechgonewild @javilopen@robiutft Let's keep going... What happens then? If anyone can create any app locally, including their own cursor, then what? Where's the moat?... One of a kind systems with network effect, Bitcoin, NFT-like systems, knockoffs are not the real deal types? It's not too hard to imagine.
@RandomU94836@businessbarista In a shallow way, yes. However, MCPs must interpret the JSON-RPC to map to the API call. If my payload has elements like "message," "slack," and key-value pairs, and if my LLM can substitute "slack" on the fly with, say "Twilio" or "Gmail," then its less friction.
@adocados@AskPerplexity@charles_r_sears@businessbarista You don’t. You need the keys—unless it’s an application that doesn’t require authentication. MCP simply allows you to send JSON-RPC requests to servers (hubs), which it maps to the API call. It removes friction and saves time while relying on LLM to form the JSON.
More in depth: User Query -> LLM (loaded with schema outlining services it can call, i.e., tools, tables, and others) -> LLM interprets the user query and constructs JSON-RPC per schema -> system sends this to the MPC server via POST (external third party) or stdin (local) -> JSON input is used to map to the appropriate API requirements for the service (may need API keys for authentication) -> the service processes the request -> the service responds with a payload -> context is passed to the LLM -> LLM uses this context to respond to the user.
E.g., user: “What tasks did I assign in # project-channel in Slack last week?” The LLM sends a JSON-RPC to the MPC server {"method": "searchMessages", "params": {"channel": "# project-channel", "from": "you", "dateRange": "last week"}}. MPC server sends an API request to Slack. In response, Slack returns a message like “Hey @ team, finish the report by Friday.” The LLM then provides a concise summary: “You assigned a report due Friday.” Afterward, if instructed to “Remind the team about the report,” the AI can again use a method call to post directly in Slack: “@ team, don’t forget the report’s due tomorrow!”
MCP serves as an abstraction layer that eliminates the need to interact directly with multiple APIs, instead providing a standardized protocol for communication with various services.
This accelerates the shift in how we experience the web and generally information flow. The internet can now be consumed whole by agents in their windows, the way the internet once consumed physical libraries.