Skip to content

MCP_Model_Context_Protocol_Client_Server.md

Latest commit

 

History

History
45 lines (24 loc) · 2.74 KB

MCP_Model_Context_Protocol_Client_Server.md

File metadata and controls

45 lines (24 loc) · 2.74 KB
graph LR
    MCPClient["MCPClient"]
    MCPServer["MCPServer"]
    MCPController["MCPController"]
    MCPClient -- "communicates with" --> MCPServer
    MCPController -- "uses" --> MCPClient
Loading

CodeBoardingDemoContact

Details

The MCP (Model Context Protocol) Client/Server subsystem is a critical part of the browser-use project, enabling the AI agent to interact with external services and expose its own capabilities.

MCPClient

This component is responsible for initiating and managing outgoing communication with external services that adhere to the Model Context Protocol. It acts as the browser-use agent's interface for consuming capabilities (tools) exposed by other MCP-compliant services. Its key responsibilities include establishing connections, registering the agent's own capabilities with a remote controller (if acting as a tool provider), and formatting/sending tool invocation requests.

Related Classes/Methods:

MCPServer

This component is responsible for handling incoming requests from MCP clients. Its primary role is to expose the browser-use agent's internal browser automation capabilities (e.g., navigation, clicking, typing) as callable tools to external MCP clients. It processes tool invocation requests, executes the corresponding browser actions, and manages the lifecycle of the browser session.

Related Classes/Methods:

MCPController

This component acts as the internal orchestrator within the browser-use agent for managing MCP connections and integrating external MCP tools. It bridges the gap between the agent's core logic and external MCP services, allowing the agent to discover and utilize tools provided by other MCP-compliant entities. It uses the MCPClient to establish connections and register tools.

Related Classes/Methods:

FAQ