A
licenseNot graded
qualityD
maintenanceA Model Context Protocol server built with mcp-framework that allows users to create and manage custom tools for processing data, integrating with the Claude Desktop via CLI.
46 npm
5
MIT
Hello-MCP
by hongsw
🚀 你好 MCP（模型上下文协议）
“Claude Desktop MCP 配置管理器设置指南工具”
한국어 버전은 아래 링크에서 확인할 수 있습니다。 한국어 버전
英文版可在以下链接获取。英文版
✨ 概述
Hello-MCP 是一款实用工具，它使 Claude Desktop 能够通过模型上下文协议 (MCP) 与外部工具进行交互。它简化了设置过程，并实现了 Claude AI 与您的自定义工具之间的无缝集成。
（英文）您好，欢迎光临！ （韩语）안녕하세요, 환영합니다！
Related MCP server: my-mcp-server
🛠️ 功能
轻松设置：Claude Desktop MCP 集成的简单单命令设置
多种模式：作为安装向导、MCP 服务器或 CLI 工具运行
内置示例工具：预先配置的工具，如电子邮件发送和简单计算
可扩展：轻松添加您自己的 MCP 工具
国际化：支持多种语言（韩语和英语）
📋 要求
🚀 快速入门
您可以使用 npx 运行 Hello-MCP，无需安装：
npx hello-mcp这将启动安装向导，指导您完成整个配置过程。
🎮 使用方法
Hi-Garak 有三种使用模式：
1️⃣ 设置模式（默认）
npx hello-mcp
# or
npx hello-mcp setup此交互模式将：
检查是否安装了 Claude Desktop
询问您的电子邮件和目的
生成 API 密钥
为 MCP 配置 Claude Desktop
自动重启 Claude Desktop（如果可能）
2️⃣ MCP 服务器模式
npx hello-mcp mcp-server这将启动 Hello-MCP 作为 Claude Desktop 可以连接的 MCP 服务器。该服务器提供 Claude 可以用来执行操作的工具。
🔑 API 密钥
您的 API 密钥存储在~/.garakrc中，每日请求次数限制为 50 次。该密钥已自动配置为与 Claude Desktop 配合使用。
📊 遥测
Hello-MCP 收集匿名使用数据以改进服务：
用户交互和性能指标
所有数据均匿名
您可以在配置中禁用遥测
🌟 使用 Claude 的技巧
设置完成后，您可以向 Claude 尝试以下提示：
“1加1”（简单计算）
“向 [your-email] 发送一封电子邮件，结果为 1 加 1”
🤝 支持
如果您遇到任何问题，请联系我们： help@garak.ai
📚 文档
如需更多示例和提示，请访问我们的入门指南：入门指南
您还可以浏览我们的交互式文档：
本地运行：
npx docsify-cli serve docs在浏览器中查看： http://localhost:3000
🚧 待办事项
如果您遇到任何问题或有任何建议，请在合适的问题跟踪系统（例如 GitHub Issues）上创建问题。请提供问题的详细描述以及重现步骤。https ://github.com/hongsw/hello-mcp/issues
Windows 支持目前正在测试中。
📄 许可证
该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅 LICENSE 文件。
Available Tools
2 toolsaddD
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | ||
| b | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
send-emailD
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | |||
| body | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
v1.0.0- First observed
add - First observed
send-email
TDQS
D1.2/5.0
Scored across 2 tools
Disambiguation2/5
The two tools, 'add' and 'send-email', have no descriptions and appear to serve completely unrelated purposes. An agent cannot determine what 'add' refers to or how it relates to sending email, creating ambiguity.
Naming Consistency2/5
The tool names follow no consistent pattern: 'add' is a bare verb while 'send-email' uses a verb-noun format with a hyphen. The lack of a shared convention makes the set feel ad hoc.
Tool Count2/5
With only two tools and no descriptions, the server appears extremely thin and under-scoped. It is unclear what domain it covers, and two unrelated tools do not form a coherent toolkit.
Completeness1/5
The server's purpose is entirely unclear from the tool names alone. 'add' and 'send-email' do not suggest any complete workflow or domain coverage, leaving obvious gaps in any conceivable use case.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.87 npm-
- AlicenseNot gradedqualityDmaintenanceA tool that helps users easily register Anthropic's Model Context Protocol in Claude Desktop and Cursor, providing ready-made MCP tools for RAG, web search, and Dify integrations.MIT
- AlicenseNot gradedqualityDmaintenanceA local Model Context Protocol (MCP) server that exposes custom tools to Claude Desktop, enabling direct interaction with your local environment. It provides a framework for building and integrating custom TypeScript tools into the Claude interface.3 npmMIT