How cookie-hoo/hello-mcp works
And represent the main components
• MCP Client: There are at least two variants—in one mode (client2stdio) that communicates via standard I/O, and in another (client2sse) that registers with a running server over HTTP using SSE.
• MCP Server: Implemented in the server.py file, it utilizes FastMCP to expose MCP tools (for example, a tool that lists directory contents) and supports both SSE and stdio executions.
• Configuration Management: Show the use of configuration (config.example.yaml, which is copied to config.yaml) to inject parameters such as the DeepSeek API key.
• When using client2sse, the client component sends registration calls and interactions to the MCP Server over HTTP (using the provided server URL).
• When using client2stdio, the communication flow is directed towards local execution or internal function calls (with the server launched via a file path).
• Configuration file as a common service that both client and server rely on.
Point out architectural patterns
• The project leverages a modular design. Separate modules (client, client2sse, client2stdio, server) indicate that it follows a component-based design where each module has a specific responsibility.
Details on relevant technologies
• Python is the core language with a structure that supports packages (observed by the __init__.py and organized module files).
• SSE (Server-Sent Events) and stdio are the two communication mechanisms.
• The DeepSeek API integration is a notable external dependency.