Kolay IK MCP by usefulapi

io.usefulapi/kolay-ik · v1.0.0 · productivity

Kolay IK MCP by usefulapi is healthy: it completed an MCP handshake in 1107 ms and exposes 30 tools.

Read employees, leave and payroll; create leave, time records and events in Kolay IK.

Endpoint: https://kolay-ik.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)	0
Handshake	Healthy
Auth needed	None
Tool count	30
Latency	1107 ms
Last checked (UTC)	2026-11-02T20:10:27.175Z

Health history

Checked (UTC)	Status	Latency	Error
2026-11-02T20:10:27.175Z	Healthy	1107

Tools (30)

`kolayik_get_me`	The Kolay IK user the API token belongs to: id, name, email, work email. A cheap check that the connection works. GET /v2/profile/me.
`kolayik_list_people`	List employees (id, first and last name), 60 per page. By default only active employees; set status to terminated for people who left. Search by name with q. Filter by hire date (active people) or termination date (terminated people). The reply has total, currentPage and lastPage; request the next p
`kolayik_get_person`	Full profile of one employee: contact data, employment dates, contract, units, compensation and custom data fields. National id numbers and bank numbers are removed. GET /v2/person/view/{id}.
`kolayik_get_person_summary`	Short profile of one employee: name, contact data, current units (company, location, department, position) and manager. GET /v2/person/view-summary/{id}.
`kolayik_get_person_leave_balances`	Leave entitlement of one employee per leave type: earned, used, carried over and unused days. GET /v2/person/leave-status/{id}.
`kolayik_list_person_trainings`	Trainings assigned to one employee. GET /v2/person/list-trainings/{id}.
`kolayik_list_person_fields`	The custom data fields a person can have (fieldToken, type, category). Use the fieldToken in kolayik_update_person and kolayik_create_person. GET /v2/person/show-available-data-fields.
`kolayik_list_units`	The organization tree: unit types (company, branch, department, position ...) and their items with ids. GET /v2/unit/show-unit-tree.
`kolayik_list_approval_processes`	The approval chains configured in the account (leave, expense and similar), with their steps and approvers. Filter by name or by a person in the steps. GET /v2/approval-process/list.
`kolayik_list_leaves`	List leave (time off) records, newest data first as the vendor orders them. Filter by status, a date range or one person. Each record has the leave type, dates, person, replacement, status (approved/waiting/rejected) and used days. GET /v2/leave/list.
`kolayik_get_leave`	One leave record with type, dates, return date, comment, person, replacement person, status and used days. GET /v2/leave/view/{id}.
`kolayik_create_leave`	WRITE: records leave for an employee and deducts the used days from their balance. The vendor may approve it immediately, and it is visible to the employee and their manager. Find the leave type id in an existing leave record (kolayik_list_leaves) or the person's balances (kolayik_get_person_leave_b
`kolayik_list_timelogs`	List time records (work hours, overtime) with person, start and end, minutes used, status and type. Filter by person, type, status and date range. The reply has searchCount, totalCount, page and limit. POST /v2/timelog/list (a read).
`kolayik_get_timelog`	One time record by id. GET /v2/timelog/view/{id}.
`kolayik_create_timelog`	WRITE: adds a time record (work hours or overtime) for an employee. With status approved it counts immediately (overtime may flow into payroll); with waiting it enters the approval process. Not idempotent: a second call creates a second record. POST /v2/timelog/create.
`kolayik_delete_timelog`	WRITE (destructive): permanently deletes one time record. This cannot be undone. DELETE /v2/timelog/delete/{id}.
`kolayik_list_transactions`	List employee transactions (expenses, advance payments, bonuses, overtime pay, deductions) with amount, currency, status, paid flag and items. Filter by person, type, status, paid and date range. POST /v2/transaction/list (a read).
`kolayik_get_transaction`	One transaction (expense, advance, bonus ...) with its items. GET /v2/transaction/view/{id}.
`kolayik_list_expense_categories`	Expense categories of the account (for example taxi, meals), optionally filtered by title or enabled state. GET /v2/expense/list-categories.
`kolayik_list_payrolls`	Payroll runs of a year: id, period, number of employees, payslips created, errors and total employer cost. Needs a token with the payroll:list scope. Use the id with kolayik_get_payroll_sheet. GET /v2/payroll/list.
`kolayik_get_payroll_sheet`	The full payroll sheet (carsaf bordro) of one payroll run: every employee's gross, net, tax and insurance columns. This is sensitive salary data of all employees (or the filtered ones). Needs a token with the payroll-sheet:view scope. Filter by name, status, salary period, insurance, tax, expense ce
`kolayik_list_events`	List company calendar events (meetings, holidays) with title, start, end and comment. Filter by text and date range. The reply has searchCount, totalCount, page and limit. GET /v2/event/list.
`kolayik_get_event`	One calendar event. GET /v2/event/view/{id}.
`kolayik_create_event`	WRITE: adds an event to the company calendar, visible to the employees who see it. Not idempotent. POST /v2/event/create.
`kolayik_update_event`	WRITE: changes the title, times or comment of a calendar event (the vendor requires title, start and end). PUT /v2/event/update/{id}.
`kolayik_delete_event`	WRITE (destructive): permanently deletes one calendar event. This cannot be undone. DELETE /v2/event/delete/{id}.
`kolayik_list_trainings`	List the trainings defined in the account. Filter by title text. The reply has searchCount, totalCount, page and limit. GET /v2/training/list.
`kolayik_get_training`	One training with its details. GET /v2/training/view/{id}.
`kolayik_create_person`	WRITE: adds a new employee (only first and last name are required). Creates a real HR record that may send the person an invitation, depending on the account settings. Not idempotent: calling it twice creates a duplicate. Further data goes in data_fields (see kolayik_list_person_fields). POST /v2/pe
`kolayik_update_person`	WRITE: changes basic data of one employee; only the fields you pass change. Pass null for an optional field to clear it. Further data goes in data_fields (see kolayik_list_person_fields). Changes the HR record immediately. PUT /v2/person/update.