Discussion on "AI Is Getting a Body. Here's What That Means."

Kavya Sree Kammari · 2026-07-21T15:23:06.561Z

Since I was a kid, I wanted JARVIS. Not a chatbot. Not a search engine. Not something that answers me. Something that actually does things. Tony Stark walks into his lab. Says "JARVIS, run diagnostics

Hey Kavya, Loved the way you’ve structured the article. The fact that you started with what’s already there (LLMs) to what’s being adopted ( Agentic AI) and then you go on to connect the dots with the “how” part of it - puts the whole article into perspective! Can’t wait for the next one…

Thank you, Ishvarya! I really appreciate the kind feedback and so glad the flow made sense. Next article is already in the works! ✨

The "read the guidebook the airline publishes" analogy for MCP is the clearest framing of it I've come across. It captures that the agent isn't hardcoded against one API, it discovers capabilities a provider chose to expose, which is what makes the pattern scale across tools. Where do you see the boundary landing on what a provider should and shouldn't expose through it?

Great observation Kartik! The rule of thumb I'd use: expose actions, not infrastructure. A provider should publish what it can do (search flights, book, cancel, check status), not raw database access or internal system internals. The boundary is capability vs infrastructure.

And this is actually a real security conversation happening right now. If a provider exposes too much through an MCP, a poorly-scoped agent could read data it shouldn't, trigger unintended actions, or become an attack surface for prompt injection. Production teams are genuinely cautious about this — which is part of why adoption has been slower than the hype suggests.

There's also an interesting industry shift happening: until recently, there was a whole ecosystem of startups, consultants, and freelancers whose job was to build the custom product or infra layer for your specific AI usecase — designing how AI plugs into your business end to end. MCP is quietly threatening that. When the protocol is standardised and any AI can discover what your service does, that bespoke integration business gets a lot harder to justify.

Going deep on this in the MCP dedicated post later in the series.

My laziness is my JARVIS moment which made me fall in love with the idea of something else doing the work for me 🤧😂

My laziness brought me into CS too honestly 🤣. If something can be automated, it should be.

Hi Kavya, Lasya shared me your blogsite. Really insightful demonstration of the ReAct loop. I see how you compared MCP to USB C. Ingenious.

Hey Siddhesh! Thanks a lot! Glad you liked the article and the MCP/USB-C comparison. Felt like the most practical way to explain it! Appreciate you taking the time to read it.

Search Hashnode

AI Is Getting a Body. Here's What That Means.

Responses8