TotemClock MCP by usefulapi
Read employees, punches, timecards and timesheets; record punches in TotemClock.
Sollte ich dies verwenden
Qualität und Sicherheit
Befunde (1)
- LOWin totemclock_get_monthly_timecard
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"totemclock": {
"url": "https://totemclock.usefulapi.io/mcp"
}
}
}Remote-Endpunkte
https://totemclock.usefulapi.io/mcpstreamable-httpWas es kann
Tool-Inventar
Tools (10)
🟢totemclock_get_organization
Return the company that owns the API key: name, slug, and timezone. Good first call to confirm which company is connected. TotemClock API: GET /api/v1/organization.
Eingabe-Schema
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_list_employees
List active employees with code, name, job title, department, hire and termination dates, and attendance mode (SCHEDULED, SINGLE_DAILY, EXEMPT, ACTUAL). Use the id in the other tools. TotemClock API: GET /api/v1/employees.
Eingabe-Schema
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_list_sites
List active company sites with address, punch policy (NONE, GEO, QR, GEO_OR_QR, GEO_AND_QR), and geofence radius in meters. TotemClock API: GET /api/v1/sites.
Eingabe-Schema
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_list_schedules
List active work schedules and which employees each one is assigned to. TotemClock API: GET /api/v1/schedules.
Eingabe-Schema
{
"type": "object",
"properties": {},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_list_punches(from, to, employeeId, limit)
List raw clock punches (CLOCK_IN, CLOCK_OUT, BREAK_START, BREAK_END) in a date-time range, optionally for one employee. Range is required. TotemClock API: GET /api/v1/punches.
Eingabe-Schema
{
"type": "object",
"properties": {
"from": {
"type": "string",
"minLength": 10,
"maxLength": 40,
"description": "Start of the range (inclusive)."
},
"to": {
"type": "string",
"minLength": 10,
"maxLength": 40,
"description": "End of the range (exclusive)."
},
"employeeId": {
"description": "Only punches for this employee id.",
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"limit": {
"description": "Maximum punches to return (1-500, default 100).",
"type": "integer",
"minimum": 1,
"maximum": 500
}
},
"required": [
"from",
"to"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟡totemclock_create_punch(externalId, employeeId, type, occurredAt, siteId, ...)
Record one clock punch for an employee (CLOCK_IN, CLOCK_OUT, BREAK_START, BREAK_END) at occurredAt. externalId makes the call safe to retry: the same externalId and payload return the existing punch. Needs the punches:write scope. TotemClock API: POST /api/v1/punches.
Eingabe-Schema
{
"type": "object",
"properties": {
"externalId": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"description": "Your own unique id for this punch, unique inside the company. Reuse it on retries."
},
"employeeId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The employee id (from totemclock_list_employees)."
},
"type": {
"type": "string",
"enum": [
"CLOCK_IN",
"CLOCK_OUT",
"BREAK_START",
"BREAK_END"
],
"description": "Punch type."
},
"occurredAt": {
"type": "string",
"minLength": 10,
"maxLength": 40,
"description": "When the punch happened, with offset, e.g. 2026-09-09T08:00:00+02:00."
},
"siteId": {
"description": "Site id (from totemclock_list_sites), if the punch has a site.",
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"note": {
"description": "Free-text note, max 500 characters.",
"type": "string",
"maxLength": 500
}
},
"required": [
"externalId",
"employeeId",
"type",
"occurredAt"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_get_employee_day(employeeId, date)
Return one employee's punches and calculated result for one day: first in, last out, worked, target, overtime, late and early-leave minutes, and anomalies. TotemClock API: GET /api/v1/employees/{employeeId}/days/{date}.
Eingabe-Schema
{
"type": "object",
"properties": {
"employeeId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The employee id (from totemclock_list_employees)."
},
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The day, yyyy-mm-dd."
}
},
"required": [
"employeeId",
"date"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_list_timecards(date)
Return the calculated daily timecard rows for all employees on one day (default: today in the company timezone). TotemClock API: GET /api/v1/timecards.
Eingabe-Schema
{
"type": "object",
"properties": {
"date": {
"description": "The day, yyyy-mm-dd. Omit for the company's current day.",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_get_monthly_timecard(month, employeeId)
Return one employee's calculated monthly timecard: each day, the causes behind the results, and monthly totals. TotemClock API: GET /api/v1/monthly-timecards.
Eingabe-Schema
{
"type": "object",
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, yyyy-mm."
},
"employeeId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The employee id (from totemclock_list_employees)."
}
},
"required": [
"month",
"employeeId"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢totemclock_get_timesheet(month, employeeId)
Return one employee's monthly timesheet: the hours and activities assigned to customers, projects and work, with the total minutes. TotemClock API: GET /api/v1/timesheets.
Eingabe-Schema
{
"type": "object",
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, yyyy-mm."
},
"employeeId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The employee id (from totemclock_list_employees)."
}
},
"required": [
"month",
"employeeId"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}Community
Nachweis