Overview
Model Context Protocol, or MCP, is used as a mechanism for connecting agents to tools, software, browsers, and other model endpoints.
An MCP server can expose a set of actions to the agent. The agent does not need to understand the internal implementation of the external system. It needs to understand the tools that are available and how to call them.
In a multi-model setup, the orchestrator can access Claude, Gemini, or Codex endpoints through configured servers. In a browser setup, Chrome DevTools can expose actions such as opening a page, clicking an element, dragging an item, reading console messages, or taking a screenshot.
MCP can therefore be understood as a capability bridge. It gives the reasoning model access to external actions.
The agent is similar to a pilot in a cockpit. It may not have constructed every system in the aircraft, but it can use the controls. Tool descriptions tell it which control performs which action.