Hello-MCP 🚀

Created By
Cookie-HOOa year ago
A Simple MCP Demo With Client & Server
Overview

What is Hello-MCP?

Hello-MCP is a simple implementation of the Model Control Protocol (MCP) that includes both a client and server, designed to help users understand the MCP protocol and its functionalities.

How to use Hello-MCP?

To use Hello-MCP, clone the project from GitHub, set up the environment, install dependencies, configure the DeepSeek API key, and run the client and server using the provided commands.

Key features of Hello-MCP?

  • MCP Client with interactive command line chat interface.
  • Supports registering MCP Server using both SSE and stdio methods.
  • MCP Server based on FastMCP with health check support and basic path utility.

Use cases of Hello-MCP?

  1. Learning and experimenting with the MCP protocol.
  2. Building custom MCP clients and servers.
  3. Integrating MCP into AI systems for standardized model interactions.

FAQ from Hello-MCP?

  • What problems does MCP solve?

MCP standardizes AI model interaction protocols and simplifies complex AI system integration.

  • How to solve DeepSeek API key configuration issues?

Ensure the api_key field in config.yaml is correctly filled and try regenerating the API key if authentication fails.

  • How to contribute code?

Contributions are welcome via GitHub; fork the project, create a feature branch, and open a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cookie-HOO
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago