179 questions
No questions match those filters.
What is MCP, and how has it changed how agents use tools?
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansBefore a common protocol existed, wiring an agent up to external tools meant writing bespoke integration code for every single service — one integration for a database, a different one for a file store, another for each API, none of it reusable across projects or models. Model Context Protocol standardizes that interface: a tool provider exposes itself as an MCP server, and any MCP-compatible agent can connect to it the same way regardless of which model or framework the agent is built on.
An MCP server can expose three kinds of things: tools the model can call, resources the model can read as context, and reusable prompt templates. The practical effect is that adding a new capability to an agent stops being an integration project — it becomes pointing the agent at an existing server, the same way installing a package beats writing a library from scratch.
The result is an ecosystem rather than a pile of one-off integrations: because the interface is shared, a server built for one team’s agent works for anyone else’s MCP-compatible agent too, which is why the number of available servers has grown quickly since the standard appeared — each new server is reusable capability for the whole ecosystem, not just the team that wrote it.