← Back to Dashboard
1. What is MCP?2. Core Architecture3. Host vs Client vs Server
Core Architecture
The Three Main Pillars
MCP architecture consists of three logical components:
- MCP Hosts: The application the user interacts with (e.g., Claude Desktop, Cursor). It bridges the gap between the LLM and the protocol.
- MCP Clients: The protocol implementation running inside the Host. It initiates the connection to servers.
- MCP Servers: Lightweight, independent programs that expose specific data (Resources), actions (Tools), or templates (Prompts).
A Typical Request Flow
When you ask "Summarize my recent GitHub PRs":
- Claude Desktop (Host) connects to your GitHub MCP Server via local
stdio. - The Host asks the Server: "What capabilities do you offer?"
- The Server replies: "I have tools:
get_prs,read_file, andsearch_repo." - The LLM decides to use
get_prs. The Host sends the execution request to the Server. - The Server executes the API call securely and returns the JSON data to the Host to display.
🧪 Knowledge Check
Press 1-4 to select1 of 3
In MCP architecture, what role does Claude Desktop play?
MCP Server
MCP Host
MCP Transport layer
MCP Proxy