Run any Skill in Manus with one click

mcp-fundamentals

Stars0

Forks0

UpdatedJanuary 20, 2026 at 08:52

core architecture of the Model Context Protocol (MCP). Use this to understand Hosts, Clients, Servers, and the JSON-RPC communication layer.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

abhishekmmgn

abhishekmmgn/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	mcp-fundamentals
description	core architecture of the Model Context Protocol (MCP). Use this to understand Hosts, Clients, Servers, and the JSON-RPC communication layer.

MCP Fundamentals

Goal

Understand the Model Context Protocol (MCP) architecture to solve the "$N \times M$" integration problem, decoupling AI models from the specific implementation details of external tools.

Core Architectural Components

1. The Host (The Application)

Definition: The container application (e.g., a desktop app, IDE, or agent platform) that manages the user experience and orchestrates tool usage.
Responsibilities:
- Creating and managing MCP clients.
- Enforcing security policies and content guardrails.
- Managing the user interaction lifecycle.

2. The Client (The Connector)

Definition: A software component embedded within the Host that maintains a 1:1 connection with a specific Server.
Responsibilities:
- Issuing commands to the server.
- Receiving and processing responses or notifications.
- Managing the session lifecycle.

3. The Server (The Provider)

Definition: A standalone program that exposes capabilities (Tools, Resources, Prompts) to the AI application.
Responsibilities:
- Tool Discovery: Advertising what tools are available.
- Execution: Receiving commands and running the actual logic/API calls.
- Formatting: Returning standardized results to the client.

The Communication Layer

Protocol: JSON-RPC 2.0

All communication is text-based and language-agnostic, relying on four standard message types:

Requests: Calls expecting a response (e.g., tools/call).
Results: Successful responses containing data.
Errors: Failure messages with codes and descriptions.
Notifications: One-way messages requiring no response (e.g., logging).

Transport Mechanisms

stdio (Standard Input/Output):
- Use Case: Local, private tools.
- Mechanism: The Host spawns the Server as a subprocess and communicates via standard I/O pipes. Best for accessing local files or scripts.
Streamable HTTP (SSE):
- Use Case: Remote or distributed tools.
- Mechanism: Uses Server-Sent Events (SSE) for streaming responses, allowing connections to remote services over standard HTTP.

More from this repository

same repository

agent-contracts

abhishekmmgn/skills

framework for implementing "Contract-Adhering Agents." Use this to define precise task specifications, deliverables, and negotiation loops to reduce ambiguity in complex workflows.

2026-01-200

agent-development

abhishekmmgn/skills

implementation patterns for Gemini agents. Use this for coding ReAct loops, defining tools in Python, and using frameworks like LangChain/LangGraph.

2026-01-200

agent-evaluation

abhishekmmgn/skills

methodologies for assessing agent capabilities, tool-use trajectories, and final response quality. Use this to implement automated testing and human-in-the-loop validation for agents.

2026-01-200

agent-interoperability-a2a

abhishekmmgn/skills

standardized protocols for agent collaboration. Use this to implement the Agent2Agent (A2A) protocol and Agent Cards to transform isolated agents into a collaborative ecosystem.

2026-01-200

agent-observability

abhishekmmgn/skills

strategies for agent observability (logging, tracing, metrics). Use this to instrument agents for debugging, performance tracking, and quality assurance.

2026-01-200

agent-ops

abhishekmmgn/skills

operationalization strategies for agents (AgentOps). Use this to manage internal/external tools, optimize agent "brain" prompts, and handle task decomposition.

2026-01-200

MCP Fundamentals

Goal

Understand the Model Context Protocol (MCP) architecture to solve the "$N \times M$" integration problem, decoupling AI models from the specific implementation details of external tools.

Core Architectural Components

1. The Host (The Application)

Definition: The container application (e.g., a desktop app, IDE, or agent platform) that manages the user experience and orchestrates tool usage.

Responsibilities:

Creating and managing MCP clients.
Enforcing security policies and content guardrails.
Managing the user interaction lifecycle.

2. The Client (The Connector)

Definition: A software component embedded within the Host that maintains a 1:1 connection with a specific Server.

Responsibilities:

Issuing commands to the server.
Receiving and processing responses or notifications.
Managing the session lifecycle.

3. The Server (The Provider)

Definition: A standalone program that exposes capabilities (Tools, Resources, Prompts) to the AI application.

Responsibilities:

Tool Discovery: Advertising what tools are available.
Execution: Receiving commands and running the actual logic/API calls.
Formatting: Returning standardized results to the client.

The Communication Layer

Protocol: JSON-RPC 2.0

All communication is text-based and language-agnostic, relying on four standard message types:

Requests: Calls expecting a response (e.g., tools/call).

Results: Successful responses containing data.

Errors: Failure messages with codes and descriptions.

Notifications: One-way messages requiring no response (e.g., logging).

Transport Mechanisms

stdio (Standard Input/Output):

Use Case: Local, private tools.
Mechanism: The Host spawns the Server as a subprocess and communicates via standard I/O pipes. Best for accessing local files or scripts.

Streamable HTTP (SSE):

Use Case: Remote or distributed tools.
Mechanism: Uses Server-Sent Events (SSE) for streaming responses, allowing connections to remote services over standard HTTP.