Connecteam MCP by usefulapi

The Connecteam company this API key belongs to: company name and company id. GET /me.

List employees (users): name, email, phone, user type (user/manager/owner), archived state, smart groups, custom fields and last login. Use it to map the user ids in shifts, time activities, timesheets, time off and tasks to names. Kiosk codes and device ids are never returned. GET /users/v1/users.

List the job schedulers (schedules) in the account with their id, name, time zone and archived state. The scheduler id is needed to list or create shifts. GET /scheduler/v1/schedulers.

List shifts of one scheduler in a time window (one row per assigned user, as Connecteam's V1 endpoint returns them): title, start/end (Unix seconds), time zone, assigned user ids, open-shift spots, job, location, published state, statuses, breaks, notes and shift tasks. Filter by assigned users, job, open or published. GET /scheduler/v1/schedulers/{schedulerId}/shifts.

One shift of a scheduler by its id, with assignments, statuses, breaks, notes and tasks. GET /scheduler/v1/schedulers/{schedulerId}/shifts/{shiftId}.

WRITE: create ONE shift in a scheduler (one assignee or one open spot: the V1 endpoint does not create group or multi-spot shifts). By default it is created as an unpublished draft (employees see nothing). With is_published=true it is published, and Connecteam notifies the assigned users unless notify_users=false. Give a title or a job_id (Connecteam requires one). For an open shift set is_open_sh

List the time clocks in the account (id, name, archived). The time clock id is needed for time activities and timesheets. GET /time-clock/v1/time-clocks.

Clock-in/clock-out records of a time clock for a date range (at most 31 days per call), grouped by user: worked shifts (start/end, job, sub-job, notes, auto clock-out), manual breaks and time off. Filter by users, jobs or activity type. GET /time-clock/v1/time-clocks/{timeClockId}/time-activities.

Payroll-ready timesheet totals of a time clock for a date range (at most 45 days, Connecteam's limit): per user and day, total/work/paid-break/unpaid-break hours (decimal), approved/submitted/locked flags and pay items by pay rule (with pay rates when defined). Filter by users, groups, jobs or approval state. GET /time-clock/v1/time-clocks/{timeClockId}/timesheet.

List jobs (the work items shifts and time are tracked against): id, title, code, color, description, GPS/geofence, assigned users/groups, parent job and sub-jobs, and the schedulers/time clocks (instance ids) they belong to. GET /jobs/v1/jobs.

One job by id, with its sub-jobs, assignments and location. GET /jobs/v1/jobs/{jobId}.

List time-off policy types (e.g. Vacation, Sick) and their policies with unit (hours/days) and accrual type. Needs the HR & Skills hub. GET /time-off/v1/policy-types.

List time-off requests overlapping a date range (at most 365 days): user, policy type, dates/times, all-day flag, status (approved/pending/denied), notes, approving manager and, for approved requests, the amount deducted. Connecteam returns only approved requests unless statuses is given. Needs the HR & Skills hub. GET /time-off/v1/requests.

List the quick-task boards in the account (id, name, archived). The board id is needed to list or create tasks. GET /tasks/v1/taskboards.

List tasks on a task board: title, assigned user ids, status (draft/published/completed), start and due time (Unix seconds), labels, sub-tasks and description. Filter by status, users, labels or task ids. GET /tasks/v1/taskboards/{taskBoardId}/tasks.

List the labels of a task board (id, name, color), for filtering tasks or labelling a new one. GET /tasks/v1/taskboards/{taskBoardId}/labels.

WRITE: create one quick task on a task board for the given users. status 'draft' keeps it hidden; 'published' sends it to the assignees' apps. Several user ids make one group task. POST /tasks/v1/taskboards/{taskBoardId}/tasks.

List forms (checklists, inspections, reports) with their questions. Filter by name or creation date. GET /forms/v1/forms.

List the submissions of one form: who submitted and when, the answers and the manager fields (status, owner, notes). Filter by submitting users and time window. GET /forms/v1/forms/{formId}/form-submissions.