Not sure I'm following. I was under the impression that MCP defines a way for LLMs to reach into the "real world". The MCP servers I've played with basically say "I'm an MCP tool, and I can fetch a Jira ticket". The LLM then has the option to call the tool.
Check this out https://smithery.ai/
Re:Underwhelming MCP vs Hype
by bschmidt45 on Monday March 17, 2025 @12:12PM
(#43390030)
They banned my other account just now, but I'm the same guy:
I see - fundamental misunderstanding on my part about what it is.
It's a chat thing - for the end user. The word "protocol" is very confusing here.
Makes sense why it didn't make sense, if that makes sense.
Re:Underwhelming MCP vs Hype
by bschmidt80 on Tuesday March 18, 2025 @02:09PM
(#43402686)
Yeah I get that there is a consumer side, I was mainly referring to the technical spec - the "protocol"
I invented something like this months ago to pull up a calculator, browser, etc. in the chat UI (try it chat.blacksand.cloud)
If you prompt what is "2 + 2" it will respond with "4" and render a calculator tool in the chat. It knows what tool to render based on this system.
I guess that is what they are formalizing.
I get it now, cool.
I wonder why there is a protocol at all for end users since you are using natural language as the ACTUAL protocol.
Is MCP not for developers?
I thought of it as like a GraphQL in that it takes over the network comms layer but for LLM queries instead of payloads.
Idk