en es ja ko zh

Hello-MCP

Name: Hello-MCP
Author: hongsw

by hongsw

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

🚀 안녕하세요 MCP(모델 컨텍스트 프로토콜)

"Claude Desktop MCP Config Manager 설정을 위한 투어 및 가이드 도구"

Node.js 버전

한국어 버전은 링크에서 변경할 수 있습니다. 영어 버전

영어 버전 은 다음 링크에서 확인하실 수 있습니다.

✨ 개요

Hello-MCP는 Claude Desktop이 Model Context Protocol(MCP)을 통해 외부 도구와 상호 작용할 수 있도록 지원하는 유용한 유틸리티 도구입니다. 설정 과정을 간소화하고 Claude AI와 사용자 지정 도구 간의 원활한 통합을 제공합니다.

(한국어) 안녕하세요, 환영합니다! (한국어) 안녕하세요, 환영합니다!

Related MCP server: my-mcp-server

🛠️ 특징

간편한 설정 : Claude Desktop MCP 통합을 위한 간단한 단일 명령 설정
다중 모드 : 설치 마법사, MCP 서버 또는 CLI 도구로 실행
내장된 샘플 도구 : 이메일 전송 및 간단한 계산과 같은 사전 구성된 도구
확장 가능 : 자체 MCP 도구를 쉽게 추가할 수 있습니다.
국제화 : 여러 언어 지원(한국어, 영어)

📋 요구 사항

Node.js 14+ 다운로드
Claude Desktop 설치됨 ( 여기서 다운로드 )
이메일 전송을 위한 인터넷 연결 GARAK API 키 생성

🚀 빠른 시작

npx를 사용하면 설치 없이 Hello-MCP를 실행할 수 있습니다.

지엑스피1

이렇게 하면 전체 구성 과정을 안내하는 설정 마법사가 시작됩니다.

🎮 사용법

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에게 다음 프롬프트를 시도해 보세요.

"1 더하기 1"(간단한 계산)
"[당신의 이메일 주소]로 1 더하기 1의 결과를 이메일로 보내세요"

🤝 지원

문제가 발생하면 help@garak.ai 로 문의해 주세요.

📚 문서

더 많은 예와 팁을 보려면 시작 가이드를 방문하세요: 시작 가이드

또한 대화형 문서를 탐색할 수도 있습니다.

로컬에서 실행: npx docsify-cli serve docs
브라우저에서 보기: http://localhost:3000

🚧 할 일

문제가 발생하거나 제안 사항이 있으시면 적절한 이슈 추적 시스템(예: GitHub Issues)에 이슈를 생성해 주세요. 이슈에 대한 자세한 설명과 재현 단계를 함께 제공해 주세요. https://github.com/hongsw/hello-mcp/issues
현재 Windows 지원이 테스트 중입니다.

📄 라이센스

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

Available Tools

2 tools

addD

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
`email`	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 updatesv1.0.0Aug 15, 2025
- First observedadd
- First observedsend-email

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

D1.2/5.0

Scored 2026-09-10 02:49 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

ResponsivenessSyncing

Resources

Related MCP Connectors

Quallaa
com.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
AI & Machine Learning Communication
2
https://www.quallaa.com/api/mcp
toolweave
io.github.andreysparish
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
App Automation AI & Machine Learning Agent Orchestration
2
https://toolweave.dev/mcp
Remote MCPA
com.remote-mcp.mcp
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.
Developer Tools Search Agent Orchestration
13
https://mcp.remote-mcp.com
hithereiamaliff-mcp-nextcloud
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
https://server.smithery.ai/@hithereiamaliff/mcp-nextcloud/mcp

Related MCP Servers

Calculator MCP Server
Developer Tools Code Execution
QuantGeekDev
A
license
Not graded
quality
D
maintenance
A 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.
Updated 2 years ago (2025-02-22 23:28 UTC)
46 npm
5
MIT
my-mcp-server
Code Execution Developer Tools
15972289829
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
Updated a year ago (2025-06-03 06:36 UTC)
66 npm
-
Quick-start Auto MCP
RAG Systems Web Scraping Developer Tools
sw-jooyeon
A
license
Not graded
quality
D
maintenance
A 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.
Updated a year ago (2025-06-19 00:35 UTC)
MIT
MCP Tools
Developer Tools
joehuangcoding
A
license
Not graded
quality
D
maintenance
A 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.
Updated 8 months ago (2026-03-08 10:27 UTC)
3 npm
MIT

🚀 안녕하세요 MCP(모델 컨텍스트 프로토콜)

"Claude Desktop MCP Config Manager 설정을 위한 투어 및 가이드 도구"

✨ 개요

🛠️ 특징

📋 요구 사항

🚀 빠른 시작

🎮 사용법

1️⃣ 설정 모드(기본값)

2️⃣ MCP 서버 모드

🔑 API 키

📊 원격 측정

🌟 클로드와 함께 사용하기 위한 팁

🤝 지원

📚 문서

🚧 할 일

📄 라이센스

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Calculator MCP Server

my-mcp-server

Quick-start Auto MCP

MCP Tools