clokio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOKIO_API_KEY | Yes | Your Clokio API key (clk_...) used for authentication. | |
| CLOKIO_BASE_URL | No | Base URL of the Clokio installation. Defaults to https://app.clokio.io | https://app.clokio.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clokio_list_tasksA | List tasks. Supports filters: project_id, status (slug), priority, assignee (employee_code), label, search, open (1 = only open tasks), created_before / due_before (YYYY-MM-DD, org timezone). Paginate with page, or crawl with cursor. Each task carries a task_url. |
| clokio_get_taskA | Get one task by id, with its full detail (assignees, labels, status, custom fields, task_url). |
| clokio_create_taskB | Create a task in a project. assignees/creator use employee_code (e.g. "00080"), not internal ids. To attribute the task to a person set creator_employee_code, otherwise it shows as the API key owner. |
| clokio_update_taskA | Update a task. Only the fields you pass are changed. status/priority/title/description/due_date are supported. |
| clokio_delete_taskA | Delete a task by id. This is irreversible. |
| clokio_set_task_assigneesA | Set a task's assignees. mode "add" appends, "replace" overwrites, "remove" removes. Assignees are employee_codes (e.g. "00080"). |
| clokio_list_task_commentsA | List the comments on a task. |
| clokio_add_task_commentA | Add a comment to a task. Set author_employee_code to attribute it to a person; otherwise it shows as the API key owner ("External System"). Use readable formatting (paragraphs, bullet lists); markdown tables are not rendered. |
| clokio_get_task_activityB | Get the activity log (audit trail) for a task. |
| clokio_list_task_dependenciesA | List a task's dependencies (blocks / waiting-on). |
| clokio_add_task_dependencyB | Add a dependency between two tasks. Circular dependencies are rejected by the API. |
| clokio_set_task_custom_fieldA | Set one custom field value on a task, identified by field_key (never field_id). An API key sees PUBLIC fields only. |
| clokio_list_projectsA | List projects, optionally filtered by a search term (name / client). |
| clokio_get_project_statusesA | A project's resolved task-status set, in order (what a task in this project may become). |
| clokio_get_project_custom_fieldsB | A project's custom-field definitions, in sort order. An API key sees PUBLIC fields only. |
| clokio_get_project_contactsC | The contacts for a project's client. |
| clokio_get_clientA | Get a client by id. |
| clokio_add_client_contactC | Add a contact to a client. |
| clokio_list_task_statusesA | The organisation-wide task-status vocabulary, with is_open per slug (including project-specific slugs). Use this to discover valid status slugs before creating/updating a task. |
| clokio_list_task_labelsA | List the available task labels (tags), with names and colors. |
| clokio_list_locationsA | List the organisation's locations. |
| clokio_list_employeesA | List employees. Returns employee_code (the stable id used everywhere else, e.g. for assignees), name, and non-PII fields. email is only returned if the key holds the employees:pii scope. |
| clokio_lookup_employeeA | Look up an employee by name or email to resolve their employee_code. Use this before assigning a task when you only know the person's name. |
| clokio_get_employee_task_statsA | One employee's open / delayed_from_open / past_due task counts. stale_days sets the 'delayed' threshold (default 7, range 1-365). A task with N assignees counts for each of them. |
| clokio_create_employeeA | Create (or reactivate) an employee. Reactivating an existing inactive employee never resets their password. A pin (4-6 digits, org-unique) can be supplied or is auto-generated; it is returned only here. |
| clokio_set_employee_statusC | Set an employee's status (active / inactive / resign). |
| clokio_attendance_dailyA | Attendance for a single date (YYYY-MM-DD, defaults to today). |
| clokio_attendance_rangeA | Attendance for a date range (max 31 days). |
| clokio_attendance_for_employeeB | One employee's attendance. Optionally scope to a date range. |
| clokio_attendance_summaryC | Monthly attendance summary. |
| clokio_clock_inA | Clock an employee in. A PIN may be required depending on org configuration. Timestamps are clamped to +/-10 minutes of server time. |
| clokio_clock_outC | Clock an employee out. |
| clokio_break_startC | Start a break for an employee. |
| clokio_break_endC | End a break for an employee. |
| clokio_list_time_entriesA | List time-tracking entries. Filterable by employee_code and date range. |
| clokio_get_balancesC | Leave / hour balances. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 36 tools
Every tool has a clearly distinct purpose: tasks, projects, employees, attendance, time entries, balances, comments, dependencies, custom fields. Even similar tools like attendance_daily vs attendance_range are scoped differently. No two tools appear to do the same thing.
All tools share the clokio_ prefix followed by a consistent verb_noun pattern (list_, get_, create_, update_, delete_, set_, add_, clock_in, break_start). The minor variation between 'add' and 'create' aligns with resource types and is predictable.
36 tools is on the higher end, but the server covers a broad domain (project management and HR), so each tool earns its place. It's not bloated with redundant or trivial tools, and the count is justified by the scope.
The tool surface is quite complete for tasks (full CRUD plus assignees, comments, dependencies, custom fields, activity) and employees (create, status, attendance, stats). Minor gaps exist, like no client creation or project update, but these don't break core workflows.