TimeHunter MCP by usefulapi
Read employee status, attendance, work reports and schedules in TimeHunter.
使うべきか
品質と安全性
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"timehunter": {
"url": "https://timehunter.usefulapi.io/mcp"
}
}
}リモートエンドポイント
https://timehunter.usefulapi.io/mcpstreamable-httpできること
ツール一覧
ツール(8)
🟢timehunter_employee_status
List every employee with their current work state: working, on break, and the start time of today's session. Good first call to get employee ids. TimeHunter API: GET /api/employees/status.
入力スキーマ
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_get_work_time_today(employee_id)
Get one employee's net working time today in seconds (totalSeconds) and the number of work sessions. TimeHunter API: GET /api/work/today.
入力スキーマ
{
"type": "object",
"properties": {
"employee_id": {
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
"description": "Employee id (UUID) from timehunter_employee_status."
}
},
"required": [
"employee_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_list_attendance(date, date_from, date_to, employee_id)
List attendance per employee and day: check-in, check-out, break times, work time and location. Defaults to today. Give date, or date_from and date_to together. TimeHunter API: GET /api/attendance.
入力スキーマ
{
"type": "object",
"properties": {
"date": {
"description": "One day (YYYY-MM-DD). Default: today.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"date_from": {
"description": "First day of a range (YYYY-MM-DD). Use with date_to.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"date_to": {
"description": "Last day of a range (YYYY-MM-DD). Use with date_from.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"employee_id": {
"description": "Employee id (UUID). Omit for all employees.",
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_get_daily_report(employee_id)
Get one employee's report for today: net work seconds and each work session with start, end and break times. The API always reports today and ignores other dates. TimeHunter API: GET /api/report/daily.
入力スキーマ
{
"type": "object",
"properties": {
"employee_id": {
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
"description": "Employee id (UUID) from timehunter_employee_status."
}
},
"required": [
"employee_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_get_weekly_report(employee_id)
Get one employee's work seconds per day for the current week (dailyTotals). TimeHunter API: GET /api/report/weekly.
入力スキーマ
{
"type": "object",
"properties": {
"employee_id": {
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
"description": "Employee id (UUID) from timehunter_employee_status."
}
},
"required": [
"employee_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_get_monthly_report(employee_id, month)
Get one employee's work seconds per day for a month (dailyTotals, days with work only). Defaults to the current month. TimeHunter API: GET /api/report/monthly.
入力スキーマ
{
"type": "object",
"properties": {
"employee_id": {
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
"description": "Employee id (UUID) from timehunter_employee_status."
},
"month": {
"description": "Month (YYYY-MM). Default: current month.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$"
}
},
"required": [
"employee_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_get_period_summary(months, date_from, date_to, employees, detail)
Get a summary per employee and month: work hours, norm, overtime, balance, late arrivals, absence days by type, and weekend or holiday work. Defaults to the previous and current month. TimeHunter API: GET /api/report/summary.
入力スキーマ
{
"type": "object",
"properties": {
"months": {
"description": "Comma-separated months (YYYY-MM). Max 13.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])(,\\d{4}-(0[1-9]|1[0-2])){0,12}$"
},
"date_from": {
"description": "Start of a date range (YYYY-MM-DD). Use with date_to instead of months.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"date_to": {
"description": "End of a date range (YYYY-MM-DD). Use with date_from instead of months.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"employees": {
"description": "Comma-separated employee names or UUIDs. Omit for all active employees.",
"type": "string",
"maxLength": 1000
},
"detail": {
"description": "true adds one row per day (in/out, lateness, day type).",
"type": "boolean"
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢timehunter_list_schedules(year, month, employee_ids)
List work schedules for one month: each day's planned start and end, and the actual presence (arrival, departure, session id). TimeHunter API: GET /api/schedules.
入力スキーマ
{
"type": "object",
"properties": {
"year": {
"type": "integer",
"minimum": 2000,
"maximum": 2100,
"description": "Year, for example 2026."
},
"month": {
"type": "integer",
"minimum": 1,
"maximum": 12,
"description": "Month, 1 to 12."
},
"employee_ids": {
"description": "Comma-separated employee UUIDs. Omit for all employees.",
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}(,[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}){0,199}$"
}
},
"required": [
"year",
"month"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}コミュニティ
エビデンス