MCP Model Context Protocol Uo9

🚀 MCP - Model Context Protocol

The Model Context Protocol (MCP) is an open standard that enables developers to establish secure bidirectional connections, integrating data sources with AI-powered tools.

📋 About MCP

The Model Context Protocol (MCP) is an open standard that allows developers to establish secure two-way connections, integrating data sources with AI-powered tools. Its architecture is straightforward: developers can expose their data via an MCP server or build AI applications (MCP clients) to connect to these servers.

👉 Learn More

MCP follows a client-server architecture, where a host application can connect to multiple servers.

🏗️ Architecture

src/ → TypeScript source code
build/ → Compiled JavaScript code

weather/
├── src/        # TypeScript source code
│   └── index.ts
├── build/      # Compiled JavaScript code
│   └── index.js
├── tsconfig.json
└── package.json

src/ Directory (TypeScript Source Code)

Purpose:

• Contains TypeScript code for development time.
• Implements MCP protocol handlers (resources, tools, prompts) here.
• Also includes logic, type definitions, SDKs, etc.

Key Files:

• index.ts → Entry point for the MCP server.
• MCP Concepts:
  • resources/ → MCP resource implementations.
  • tools/ → Functions callable by LLMs.
  • prompts/ → Prompt templates / management.

build/ Directory (Compiled JavaScript Code)

Purpose:

• Holds the runtime code after TS compilation.
• This is the folder that Claude Desktop interacts with via: node build/index.js

Features:

• After compilation, it's production-ready JavaScript code.
• No need for TS at this stage.
• Clear and deployable output.

⚙️ Data Flow Pipeline

graph LR
    A[Developers write TS code] --> B[src/index.ts]
    B --> C[tsc TypeScript compiler]
    C --> D[build/index.js]
    D --> E[Node.js runtime]
    E --> F[Claude Desktop IPC]

What Happens After index.js

Once your index.js is ready, the process is as follows:

Claude Desktop ↔ stdio ↔ Server Transport ↔ McpServer ↔ Tools (1)