Hiworks Mail MCP
<a href="https://glama.ai/mcp/servers/@beylessai/hiworks-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@beylessai/hiworks-mcp/badge" />
</a>
# Hiworks Mail MCP
하이웍스 메일 시스템과 연동하여 메일 조회 및 전송을 할 수 있는 MCP(Model Context Protocol) 서버입니다.
## MCP 설정
Claude Desktop이나 Cursor AI의 MCP 서버 설정에 아래와 같이 추가합니다.
```json
{
"mcpServers": {
"hiworks-mail-mcp": {
"command": "npx",
"args": ["-y", "hiworks-mail-mcp@latest"],
"env": {
"HIWORKS_USERNAME": "your.email@hiworks.com",
"HIWORKS_PASSWORD": "your_password"
}
}
}
}
```
- `HIWORKS_USERNAME`: 하이웍스 이메일 주소
- `HIWORKS_PASSWORD`: 하이웍스 계정 비밀번호
## 서버 설정
기본적으로 다음 서버 설정을 사용합니다:
- POP3: pop3s.hiworks.com:995 (SSL)
- SMTP: smtps.hiworks.com:465 (SSL/TLS)
## 주의사항
- 계정 정보는 안전하게 관리해주세요.
- 대량 메일 발송 시 하이웍스의 정책을 준수해주세요.
## 라이선스
이 프로젝트는 MIT 라이선스 하에 배포됩니다.
자세한 내용은 [LICENSE](./LICENSE) 파일을 참고하세요.
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: read_email retrieves emails, read_username fetches usernames, search_email finds emails based on criteria, and send_email sends emails. The descriptions are straightforward and unambiguous, making tool selection easy for an agent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., read_email, send_email). This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 4 tools, the count is reasonable for an email management server, covering core operations like reading, searching, and sending emails, plus username retrieval. It is slightly lean but well-scoped for basic functionality, though additional tools like deleting or managing folders might enhance completeness.
The tools cover essential email operations (read, search, send) and username access, but there are notable gaps in lifecycle management, such as deleting emails, managing folders, or handling attachments. While agents can perform basic tasks, the lack of update or delete functions limits full email workflow coverage.