Hello-MCP logo

Hello-MCP

by Cookie-HOO

A simple implementation of MCP (Model Control Protocol) client and server. Helps understand what MCP protocol is and how it works.

View on GitHub

Last updated: N/A

What is Hello-MCP?

Hello-MCP is a project providing a basic MCP client and server implementation. It serves as a learning tool to understand the MCP protocol and build custom MCP clients and servers.

How to use Hello-MCP?

To use Hello-MCP, clone the repository, install dependencies using uv, configure the DeepSeek API key, and run the client and server using provided Python scripts. You can choose between stdio and SSE transport methods.

Key features of Hello-MCP

  • Supports registering MCP Server (both SSE and stdio methods)

  • Interactive command line chat interface

  • Supports DeepSeek API conversations

  • Streamed response output

  • Simple server based on FastMCP (supports both SSE and stdio)

  • Provides a basic path utility

  • Health check support

Use cases of Hello-MCP

  • Learning the fundamentals of MCP

  • Building custom MCP clients

  • Building custom MCP servers

  • Experimenting with AI agent interactions

FAQ from Hello-MCP

What problems does MCP solve?

MCP (Model Control Protocol) addresses: 1. Standardizing AI model interaction protocols 2. Providing unified tool calling specifications 3. Simplifying complex AI system integration 4. Enabling modular and reusable model capabilities

History of MCP

MCP development timeline: 1. 2023: Concept introduced by Anthropic (Claude's parent company) 2. 2024: Multiple open-source implementations emerged 3. 2025: Became a standard protocol for AI system integration 4. Present: Widely used in various AI agent systems

Current state of MCP

Main application scenarios: 1. AI assistant systems 2. Automated workflows 3. Multi-model collaboration platforms 4. Enterprise AI solutions. Popular implementations include FastMCP, PyMCP etc.

How to solve DeepSeek API key configuration issues?

Ensure: 1. api_key field in config.yaml is correctly filled 2. No extra spaces or quotes in the key 3. Try regenerating API key if authentication fails

Port already in use when starting server?

Solutions: 1. Check processes using port with lsof -i :8000 2. Terminate process or change server port 3. Update client registration URL