docs: update template count badge (82 → 83)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
a858dceda0
commit
29f778daf7
5 changed files with 335 additions and 5 deletions
|
|
@ -510,7 +510,20 @@ Hooks allow programmatic control over Claude's actions:
|
|||
|
||||
MCP (Model Context Protocol) servers extend Claude Code with additional tools.
|
||||
|
||||
### How MCP Works
|
||||
### MCP Architecture Overview
|
||||
|
||||
> **💡 Visual Guide**: The following diagram illustrates how MCP creates a secure control layer between LLMs and real systems. The LLM layer has **no direct data access** - the MCP Server enforces security policies before tools can interact with databases, APIs, or files.
|
||||
|
||||

|
||||
|
||||
*Figure 1: MCP Architecture showing separation between thinking (LLM), control (MCP Server), and execution (Tools). Design inspired by [Dinesh Kumar's LinkedIn visualization](https://www.linkedin.com/posts/dinesh-kumar-6b0528b4_model-context-protocol-mcp-why-it-came-activity-7419969525795782656-VoFh), recreated under Apache-2.0 license.*
|
||||
|
||||
**Key security boundaries**:
|
||||
- **Yellow layer (LLM)**: Reasoning only - **No Data Access**
|
||||
- **Orange layer (MCP Server)**: Security control point (policies, validation, logs)
|
||||
- **Grey layer (Real Systems)**: Protected data - **Hidden From AI**
|
||||
|
||||
### How MCP Works (Technical Details)
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue