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.
9
5
MIT
Hello-MCP
by hongsw
Provides a runtime environment for the MCP server, required for version 14 or higher to support the tool functionality.
Used to display status badges for Node.js version and license information in the project documentation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Hello-MCPsend an email to john@example.com with today's weather summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🚀 Hello MCP(Model Context Protocol)
"Tour and Guide Tool for Setting Up Claude Desktop MCP Config Manager"
한국어 버전은 아래 링크에서 확인할 수 있습니다. 한국어 버전
English Version is available at the following link. English Version
✨ Overview
Hello-MCP is a helpful utility tool that enables Claude Desktop to interact with external tools via the Model Context Protocol (MCP). It simplifies the setup process and provides a seamless integration between Claude AI and your custom tools.
(English) Hello, Welcome! (Korean) 안녕하세요, 환영합니다!
Related MCP server: my-mcp-server
🛠️ Features
Easy Setup: Simple one-command setup for Claude Desktop MCP integration
Multiple Modes: Run as a setup wizard, MCP server, or CLI tool
Built-in Sample Tools: Pre-configured tools like email sending and simple calculations
Extensible: Easily add your own MCP tools
Internationalization: Supports multiple languages (Korean and English)
📋 Requirements
Node.js 14+ Download
Claude Desktop installed (Download here)
Internet connection for Email Sending GARAK API key generation
🚀 Quick Start
You can run Hello-MCP without installation using npx:
npx hello-mcpThis will start the setup wizard that guides you through the entire configuration process.
🎮 Usage
Hi-Garak can be used in three different modes:
1️⃣ Setup Mode (Default)
npx hello-mcp
# or
npx hello-mcp setupThis interactive mode will:
Check if Claude Desktop is installed
Ask for your email and purpose
Generate an API key
Configure Claude Desktop for MCP
Restart Claude Desktop automatically (when possible)
2️⃣ MCP Server Mode
npx hello-mcp mcp-serverThis starts Hello-MCP as an MCP server that Claude Desktop can connect to. The server provides tools that Claude can use to perform actions.
🔑 API Keys
Your API key is stored in ~/.garakrc and has a daily limit of 50 requests. The key is automatically configured for use with Claude Desktop.
📊 Telemetry
Hello-MCP collects anonymous usage data to improve the service:
User interactions and performance metrics
All data is anonymized
You can disable telemetry in the configuration
🌟 Tips for Using with Claude
After setup, you can try these prompts with Claude:
"1 add 1" (Simple calculation)
"Send an email to [your-email] with the result of 1 add 1"
🤝 Support
If you encounter any issues, please contact us at help@garak.ai
📚 Documentation
For more examples and tips, visit our getting started guide: Getting Started Guide
You can also browse our interactive documentation:
Run locally:
npx docsify-cli serve docsView in your browser: http://localhost:3000
🚧 TODO
If you encounter any problems or have suggestions, please create an issue on a suitable issue tracking system (e.g., GitHub Issues). Provide a detailed description of the issue and steps to reproduce it. https://github.com/hongsw/hello-mcp/issues
Windows support is currently under testing.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
2 toolsaddD
ParametersJSON Schema
| 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
ParametersJSON Schema
| 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 issues
Related MCP Connectors
- QuallaaOAuthcom.quallaa
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.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
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.25-
- 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 gradedqualityCmaintenanceA 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.9MIT