MCP Server Learning

🚀 Learning the MCP Protocol

This project focuses on learning the MCP protocol, including implementing related functions and understanding key concepts.

🚀 Quick Start

This README is about learning the MCP protocol, including tasks to be completed and key learning points.

✨ Features

• Implement sampling method: https://modelcontextprotocol.io/docs/concepts/sampling
• Implement root directories.

📚 Documentation

To - Do List

• Implement the sampling method at https://modelcontextprotocol.io/docs/concepts/sampling.
• Implement root directories.

Learning Points

• There are two transmission methods:
  • Via stdio. Here, you need to provide the path to a server binary for the client to use.
  • Via sse. Here, you need to provide the network address of the server.
    • This transmission method seems more versatile to me. It allows the server to be deployed independently of the client.
• I really wanted to use fastify to build the server, but I couldn't get it to work with the existing SDK.
  • This is a great opportunity to learn how to write such a server using only Node.js!
• Core primitives related to MCP include:
  • Resources – Think of these as data (e.g., PDFs, database records, etc.) that can be used to shape the correct response based on user queries.
  • Prompts – Consider these as the prompt statements defined below the text box sometimes seen in the "prompt - to - x" process.
  • Tools – These allow the LLM to perform actions on behalf of the user. The server is responsible for invoking tools and using the results to respond to the client. The client's task is to pass these results to the LLM.
  • Sampling – I'm not entirely sure about these yet.
  • Root directories – They define the "boundaries" of the server. For example, if your server exposes a tool that interacts with the file system, you can "restrict" this tool to a specific directory by including it in the "root directories".
  • Transmission methods – They have been mentioned above. There are two transmission methods, STDIO and SSE. As for the message format, it is based on the JSON - RPC 2.0 protocol.
• I really like the built - in error handling in the SDK.
  • If I throw an error in the server tool callback function, the client SDK will handle the error and respond accordingly.