Shrutam CCA-F Crash › Domain 2 › d2-l01-mcp-overview Hinglish English →

What is MCP? — Model Context Protocol in 12 Minutes

Domain 2 · 20% ~12 min Hinglish narration

Audio-only (commute / mobile data)

Same Saavi narration, smaller file. Opus 48k preferred — auto-selected by your browser.

Scenario anchor

Aap Aaranya IT ke ek senior architect hain — client hai ASX-India, aur unka new AI assistant har trade-alert ke saath live market data, internal risk APIs, aur compliance docs simultaneously access karna chahta hai. Aap soch rahe hain: "Har tool ke liye alag integration likhoon? Ya koi standard contract hai?" Yahi problem MCP solve karta hai — ek single, versioned protocol jo aapke LLM aur enterprise tools ke beech ek API-gateway jaisi structured boundary establish karta hai.

Key Takeaways

MCP defines a versioned, JSON-schema-validated contract between an LLM host and external tools — think of it as the service-mesh sidecar for AI tool invocation: discovery, auth context, and structured I/O in one protocol.
Tool registration in MCP is declarative: each tool publishes an input/output JSON schema to the MCP server, enabling the LLM to perform capability discovery at runtime without hard-coded API knowledge.
Context injection is MCP's primary production value — it lets the host process selectively push resources, memory state, and retrieved documents into the LLM context window through a single, auditable channel rather than ad-hoc prompt concatenation.
Memory anchor for exam pressure: MCP is to LLM-tool integration what an API gateway is to microservices — one versioned, schema-enforced entry point that handles routing, capability negotiation, and context relay.

← Previous lesson Same lesson in English Next lesson → Back to overview