hello-py-mcp

MCPAI代理

提供方 HemingwayLee

AI代理 Streamable HTTP 会话登录 社区 / 第三方 Claude DesktopClaudeVS CodeContinue
查看接入方式

A Model Context Protocol-based greeting server that provides a hello tool over stdio or HTTP, and can be integrated with AI clients such as Claude Desktop, Claude Code, and Ollama for personalized greeting calls.

一句话选型结论

按资料字段整理

hello-py-mcp 属于AI代理类 MCP 服务器,Streamable HTTP,会话登录,可直接接入 Claude Desktop、Claude、VS Code 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式Streamable HTTP 鉴权会话登录 部署方式支持远程部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Blend Deployment MCP Server Greeting Tool HTML AI Integration stdio Transport HTTP Transport Developer Tool Claude Desktop Ollama

支持客户端

适用场景

Blend DeploymentMCP ServerGreeting Tool

安装与配置

Streamable HTTP 会话登录
新一代远程传输,替代 SSE
/absolute/path/to/hello-py-mcp/venv/bin/python /absolute/path/to/hello-py-mcp/server.py

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
hello-py-mcp当前 未标注 Streamable HTTP 支持远程部署 有 2026-11-16
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方HemingwayLee上游标注的维护方 HemingwayLee
分类AI代理本站按上游分类展示
连接方式Streamable HTTP新一代远程传输,替代 SSE
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-16上游最后核验时间

详细介绍

10.3 KB
来自项目仓库与上游目录的原文,未做删改

Hello MCP Server

A simple MCP (Model Context Protocol) server that provides a greeting tool,
built with the MCP Python SDK v2 (MCPServer).
* It is not necessary to listen on a port. The default transport is stdio.
* It talks to the client over standard input and output, so whatever (e.g., Ollama, Claude Code) launches it as a subprocess (like our MCP client) communicates with it directly

Terminology

In MCP, "server" names the program's role, not whether it uses the network. This
project is a stdio MCP server (also called a local MCP server). The MCP spec defines
three roles:

Role What it is In this project
Host The app the user works in, which runs the model Claude Desktop, Claude Code, or Continue.dev / Open WebUI with Ollama
Client The connection the host opens to one server Built into each host, or client/test_client.py
Server The program that provides tools, resources and prompts server.py (stdio) or http_server.py (HTTP)

The transport (stdio or streamable-http) only decides how messages travel. With
stdio, the client starts the server as a subprocess, so no port is needed.

Prerequisites

  • Python 3.10 or higher (mcp won't install on older versions; on macOS the
    system python3 may be 3.9, so use a newer one, e.g. from Homebrew or uv)

Installation

  1. Create and activate a virtual environment:```bash
    python3 -m venv venv # make sure this python3 is 3.10+
    source venv/bin/activate # On Windows: venv\Scripts\activate

2. Install dependencies:```bash
pip install -r requirements.txt

Or using pyproject.toml:```bash
pip install -e .


## Running the Server

Run the server directly:```bash
python server.py

The server communicates over stdio and is designed to be launched by an MCP client,
so running it by hand just waits for input (press Ctrl+C to exit). To try it out
interactively, use the MCP Inspector (see Testing with MCP Inspector).

> Note: MCP clients usually launch the server with an absolute command path and
> without activating your virtualenv. In the client configs below, point command at
> the virtualenv's interpreter (e.g. /absolute/path/to/hello-py-mcp/venv/bin/python,
> or venv\Scripts\python.exe on Windows), not a bare python. Otherwise the
> client may pick a Python that doesn't have mcp installed.

Running the HTTP Server

http_server.py provides the same hello tool over the
Streamable HTTP transport instead of stdio. It listens on 0.0.0.0:1234, so other
machines on your network can reach it too.

Start it and leave it running (with HTTP, clients connect to a running server instead
of launching it):```bash
venv/bin/python http_server.py


The MCP endpoint is `http://127.0.0.1:1234/mcp` (from another machine, use this
computer's IP address instead of `127.0.0.1`).

> **Warning:** The server has no authentication. Anyone who can reach port 1234 can
> call its tools.

### Using it from a browser

Opening `http://127.0.0.1:1234/mcp` directly in a browser **won't work**. The endpoint
speaks MCP (JSON-RPC with a handshake), not plain web pages, so the browser just gets
an error:```json
{"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"Bad Request: Missing session ID"}}

An MCP client first sends POST /mcp with an initialize message. The server replies
with a session ID in the Mcp-Session-Id header, and the client includes that header
in every later request. A browser's plain GET /mcp skips the handshake and has no
session ID, so the server rejects it.

Use the MCP Inspector, a web UI that acts as an MCP client (requires Node.js):

  1. With http_server.py running, start the Inspector in another terminal:bash npx @modelcontextprotocol/inspector

  2. It opens a page in your browser (usually http://localhost:6274). If it doesn't,
    open the URL printed in the terminal, including its MCP_PROXY_AUTH_TOKEN part.

  3. In the left panel, set:
    - Transport Type: Streamable HTTP
    - URL: http://127.0.0.1:1234/mcp
  4. Click Connect.
  5. Open the Tools tab, click List Tools, then select hello.
  6. Enter a name (e.g. Alice) and click Run Tool. The result is Hello, Alice!.

Using the plain HTML client

http_client/index.html is an MCP client written in plain
HTML and JavaScript, with no libraries or build step. With http_server.py running,
open the file in your browser (double-click it, or open http_client/index.html on
macOS), then click Connect, List Tools and Run Tool.

The Protocol log on the page shows every HTTP request and response, so you can see
each step the Inspector normally hides:

  1. initialize (POST): the handshake. The server replies with its info and an
    Mcp-Session-Id header.
  2. notifications/initialized (POST): confirms the handshake (HTTP 202, no body).
  3. tools/list and tools/call (POST): sent with the Mcp-Session-Id and
    MCP-Protocol-Version headers.
  4. Disconnect sends DELETE to end the session.

This works because http_server.py enables CORS. A page opened from disk has the
origin null, which differs from http://127.0.0.1:1234, so the browser blocks its
requests unless the server allows them. The server also exposes the Mcp-Session-Id
header, which JavaScript can't read otherwise.

> Note: CORS allows every origin (*), so any web page open in your browser could
> call this server too. That's fine for this demo, but restrict allow_origins for
> anything real.

Using it with Claude Code

Register it by URL instead of by command:```bash
claude mcp add --transport http hello-http http://127.0.0.1:1234/mcp


## Available Tools

### `hello`

Says hello to someone.

**Parameters:**
- `name` (string, required): The name of the person to greet

**Example response:** `Hello, Alice!`

## Using with Claude Desktop

Add this to your Claude Desktop configuration file:

**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
**Windows:** `%APPDATA%\Claude\claude_desktop_config.json````json
{
  "mcpServers": {
    "hello": {
      "command": "/absolute/path/to/hello-py-mcp/venv/bin/python",
      "args": ["/absolute/path/to/hello-py-mcp/server.py"]
    }
  }
}

Replace /absolute/path/to/hello-py-mcp with the actual path to this project, then restart Claude Desktop.

Using with Claude Code

Register the server with Claude Code:```bash
% claude mcp add hello -- /absolute/path/to/hello-py-mcp/venv/bin/python /absolute/path/to/hello-py-mcp/server.py


* The packages in venv will be included by above command
Then run `claude mcp list` to check that it's connected, or type `/mcp` inside a Claude Code session.```bash
% claude mcp list
claude.ai Claude Docs: https://api.anthropic.com/v1/pages/mcp - ✔ Connected
claude.ai Gmail: https://gmailmcp.googleapis.com/mcp/v1 - ✔ Connected
claude.ai Google Drive: https://drivemcp.googleapis.com/mcp/v1 - ✔ Connected
claude.ai Google Calendar: https://calendarmcp.googleapis.com/mcp/v1 - ✔ Connected
hello: /Users/ywlee/Desktop/code/projects/hello-py-mcp/venv/bin/python3
/Users/ywlee/Desktop/code/projects/hello-py-mcp/server.py - ✔ Connected

Use the prompt Use the hello tool to greet Alice in claude code```

Claude Code v2.1.323
Opus 5.5 · Claude Pro
~/Desktop/code/projects/hello-py-mcp

❯ Use the hello tool to greet Alice

Called hello

I called the hello tool with the name Alice, and it returned: "Hello, Alice!"

✻ Sautéed for 4s · done 3:13 PM


## Using with Ollama

Ollama doesn't natively support MCP servers, but you can use them together through various methods:

### Option 1: Using Continue.dev (VS Code/JetBrains)

Continue.dev is an IDE extension that supports both Ollama and MCP servers.

1. Install the Continue extension in VS Code or JetBrains
2. Configure your `~/.continue/config.json`:```json
{
  "models": [{
    "title": "Ollama",
    "provider": "ollama",
    "model": "llama3.2"
  }],
  "mcpServers": {
    "hello": {
      "command": "/absolute/path/to/hello-py-mcp/venv/bin/python",
      "args": ["/absolute/path/to/hello-py-mcp/server.py"]
    }
  }
}

Replace /absolute/path/to/hello-py-mcp with the actual path to this project and adjust the Ollama model name as needed.

Option 2: Using Open WebUI

Open WebUI supports MCP servers and works with Ollama.

  1. Install and run Open WebUI (connects to Ollama by default)
  2. Configure MCP server in Settings → Tools → MCP Servers

Option 3: Custom Integration

You can build a custom client using the MCP Python SDK and Ollama's API:```python
import asyncio
from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client
import ollama

async def main():
# Connect to MCP server
server_params = StdioServerParameters(
command="python",
args=["server.py"]
)

async with stdio_client(server_params) as (read, write):
    async with ClientSession(read, write) as session:
        await session.initialize()

        # List available tools
        tools = await session.list_tools()
        print(f"Available tools: {tools}")

        # Use Ollama to generate a response
        response = ollama.chat(
            model='llama3.2',
            messages=[{
                'role': 'user',
                'content': 'Say hello to Alice'
            }]
        )

        # Call MCP tool based on LLM response
        result = await session.call_tool("hello", {"name": "Alice"})
        print(result)

if name == "main":
asyncio.run(main())


## Automated Test Client

`client/test_client.py` starts the server over stdio and runs
end-to-end protocol checks (handshake, ping, tools/list, valid and invalid tool calls).
It exits with a non-zero status if any check fails:```bash
python client/test_client.py

To test http_server.py instead, start it and pass its URL:```bash
python client/test_client.py http://127.0.0.1:1234/mcp


See `client/README.md` for details.

## Testing with MCP Inspector

You can test the MCP server directly using the MCP Inspector (requires Node.js).
Run this from the project directory with the virtualenv activated:```bash
npx @modelcontextprotocol/inspector python server.py

This opens a web interface where you can test your MCP server's tools manually, regardless of which LLM you plan to use.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
hello-py-mcp 怎么安装?

在客户端按下面的安装命令接入:/absolute/path/to/hello-py-mcp/venv/bin/python /absolute/path/to/hello-py-mcp/server.py。装完在客户端配置里引用同一个包或端点。

hello-py-mcp 怎么在 Claude Desktop、Claude、VS Code 里配置?

它的传输方式是Streamable HTTP,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

hello-py-mcp 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

hello-py-mcp 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

hello-py-mcp 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、VS Code、Continue、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

hello-py-mcp 能提供哪些能力?

资料显示能力标签包括 Blend Deployment、MCP Server、Greeting Tool、HTML、AI Integration、stdio Transport。具体工具清单以官方文档为准。

hello-py-mcp 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

hello-py-mcp 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为Streamable HTTP。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-16。