Connecteam MCP
for AI agents

• get_account read

  Get account information

  Get the connected Connecteam account's company id and name. Also the cheapest way to confirm the connection is alive.

• list_sales_locations read

  List sales locations

  List the branches, stores or sites sales are recorded against. Every other sales call needs a location id from here.

• create_sales_location write

  Create a sales location

  Create a branch, store or site to record sales against.

• get_daily_sales read

  Get daily sales

  Daily sales totals per location over a date range, with both actual and projected figures. Days with no data are omitted rather than returned as zero.

• set_projected_sales write

  Set projected sales

  Set the sales TARGET for a location on one or more days. This never changes actual sales, which come from transactions. Each date may appear once.

• create_sales_transactions write

  Record sales transactions

  Record one or many sales against locations. This is what moves ACTUAL daily sales totals, unlike setting a projection.

• delete_sales_transaction write

  Delete a sales transaction

  Delete one recorded sale by id. The location's daily total is recalculated.

• delete_sales_transactions write

  Delete sales transactions in a period

  Permanently delete EVERY transaction at one location between two times. There is no undo and no per-transaction filter, so scope the window tightly.

• create_daily_note write

  Create a daily note

  Post a note on a schedule for one date, visible to the users or groups you name. This is the roster's day-level message.

• get_daily_note read

  Get a daily note

  Get one daily note by id. There is no endpoint to list notes, so the id must come from elsewhere.

• update_daily_note write

  Update a daily note

  Change a daily note's text or who can see it.

• delete_daily_note write

  Delete a daily note

  Delete a daily note from a schedule.

• list_conversations read

  List chat conversations

  List team chats and channels on the account. Private conversations are excluded. This API cannot read messages, only list conversations and send.

• create_conversation write

  Create a chat or channel

  Create a team chat (everyone posts) or a channel (admins broadcast). Needs at least one user or smart group. Messages can then be sent into it.

• send_message write

  Send a chat message

  Send a message into a team chat or channel AS A CUSTOM PUBLISHER, not as a person. senderId is a publisher id from connecteam_list_publishers.

• send_private_message write

  Send a private message

  Send a direct message to one user as a custom publisher, starting the conversation if none exists. There is no way to read their reply through this API.

• list_publishers read

  List custom publishers

  List the custom publishers messages can be sent as. Every chat send needs a senderId from here.

• list_pay_rates read

  List pay rates

  Read employees' pay rates in effect over a date range, optionally with their full change history. Built for payroll integration. Range cannot exceed 365 days.

• set_pay_rates write

  Set pay rates

  Set pay rates for up to 500 employees from an effective date. An existing rate on the same date is replaced; otherwise it is added to their history.

• delete_pay_rate write

  Delete a pay rate

  Delete one employee's pay rate entry by its effective date. Cannot be undone, and fails if it would affect approved or locked timesheet days.

• list_onboarding_packs read

  List onboarding packs

  List the company's onboarding packs. Assigning someone needs a pack id from here.

• list_onboarding_pack_assignments read

  List onboarding pack assignments

  List who is assigned to one onboarding pack, and how far through it they are.

• assign_users_to_onboarding_pack write

  Assign users to an onboarding pack

  Assign up to 500 users to an onboarding pack. All or nothing: one invalid user id and no assignments are created at all.

• list_pay_rule_policies read

  List pay rule policies

  List the account's pay rule policies, the rules that decide how hours convert into paid time.

• assign_user_to_pay_rule_policy write

  Assign a user to a pay rule policy

  Put a user on a pay rule policy from an effective date. An earlier effective date than their current assignment REPLACES and removes it.

• list_users read

  List users

  List users (employees) on the account. Filter by ids, names, phone, email, status, or by createdAt/modifiedAt/lastLogin to sync only what changed.

• create_users write

  Create users

  Create one or many users in a single call. Takes an array, so onboarding a whole team costs one request rather than one per person.

• update_users write

  Update users

  Update one or many users. Identify each by userId, or set editUsersByPhone to match on phone instead. Set isArchived false to restore an archived user.

• archive_users write

  Archive users

  Archive one or many users by id. Archiving is reversible: restore with connecteam_update_users and isArchived false. Permanent deletion is deliberately not offered.

• list_custom_fields read

  List custom fields

  List the account's user custom field definitions. Read this to turn the numeric customFieldId values on a user into names, and to find a dropdown field's id before setting it.

• list_custom_field_options read

  List custom field options

  List the dropdown options for one custom field. Setting a dropdown value on a user needs the option ID from here, not the option's text.

• list_custom_field_categories read

  List custom field categories

  List the categories user custom fields are grouped under.

• list_smart_groups read

  List smart groups

  List smart groups (dynamic user groups). Groups marked isAutomaticallyCreated are owned by a dropdown custom field and cannot be edited or deleted here.

• create_smart_group write

  Create smart group

  Create a dynamic smart group under a segment. Membership follows the filters, so users matching them are added automatically as they change.

• update_smart_group write

  Update smart group

  Update a smart group. Changing filters replaces the current rules and can change who is in the group. Automatically created groups cannot be edited.

• delete_smart_group write

  Delete smart group

  Delete a smart group. The users stay; only the grouping goes. Automatically created groups cannot be deleted here.

• list_smart_group_segments read

  List smart group segments

  List the segments smart groups are organised under. A segment id is required to create a smart group.

• create_smart_group_segment write

  Create smart group segment

  Create a segment to organise smart groups under.

• create_user_note write

  Add a note to a user

  Add a note to a user's profile. Write-only: this API has no way to read notes back, so do not promise to check or find one afterwards.

• update_user_performance write

  Record performance data

  Set performance metric values for one user on one date, replacing any existing value for that date. Write-only: this API cannot read performance data back, and not every user can carry every indicator — an ineligible one is rejected with a bare 400.

• list_performance_indicators read

  List performance indicators

  List the account's performance metrics. Recording a performance value needs an indicator id from here.

• list_pending_users read

  List pending users

  List people waiting for an admin to approve them onto the account, optionally filtered by status.

• create_pending_users write

  Create pending users

  Submit one or many join requests for an admin to approve, rather than creating users directly.

• update_pending_user_statuses write

  Approve or decline pending users

  Approve or decline one or many pending join requests. Approving creates the user on the account.

• update_pending_user write

  Update a pending user

  Correct the details on a pending join request before it is approved.

• delete_pending_user write

  Delete a pending user

  Delete a pending join request. This removes the request only, never an existing user.

• get_user_assignments read

  Get a user's assignments

  List which time clocks, schedulers, forms, tasks and other assets a user is assigned to, plus their smart groups.

• list_time_clocks read

  List time clocks

  List the account's time clocks. Every other time clock call needs an id from here, so read this first. Includes archived clocks, flagged with isArchived.

• list_time_activities read

  List time activities

  Read recorded shifts, manual breaks and time off for a date range, grouped by user. This is the detail behind a timesheet. Both dates are required.

• create_time_activities write

  Add recorded time

  Add completed shifts and manual breaks for one or many users at once. This is the admin correction path (adding hours after the fact), not clocking someone in live.

• update_time_activities write

  Correct recorded time

  Adjust existing shifts and breaks by their activity ids, for one or many users at once. Use connecteam_list_time_activities to get the ids first.

• delete_time_activity write

  Delete a recorded shift or break

  Delete one recorded shift or manual break by its activity id. Fails if the day is locked or the timesheet approved. Time off cannot be deleted here.

• clock_in write

  Clock a user in

  Start a work period for a user now. To add hours for a shift that already finished, use connecteam_create_time_activities instead.

• clock_out write

  Clock a user out

  End a user's currently open work period. There is no shift id to pass; Connecteam closes whichever shift is open.

• list_manual_breaks read

  List manual break types

  List the break types configured on a time clock (name, paid or unpaid, duration), and whether manual breaks are enabled at all. Starting a break needs an id from here.

• clock_in_manual_break write

  Start a break

  Start a manual break for a user. If they are clocked into a shift on this clock, it is closed automatically and the break starts in the same call.

• clock_out_manual_break write

  End a break

  End a user's open break. By default their shift resumes on the same job. Set isResumeShift false to end the working day instead. Mandatory breaks cannot end early.

• list_shift_attachments read

  List shift attachment fields

  List the extra fields a time clock asks employees to fill in on a shift, including dropdown options.

• list_geofences read

  List geofences

  List the geofenced sites on a time clock, with their radius, jobs and what happens when someone clocked in leaves.

• get_geofence read

  Get a geofence

  Get one geofenced site on a time clock by id.

• create_geofences write

  Create geofences

  Add one or many geofenced sites to a time clock. Radius must be 75 to 1524 metres. Latitude and longitude are strings here, not numbers.

• delete_geofence write

  Delete a geofence

  Delete a geofenced site from a time clock. Recorded hours are unaffected.

• get_timesheet_totals read

  Get timesheet totals

  Total hours per employee per day for payroll, in decimal hours, by pay rule, with automated unpaid breaks already deducted. Maximum 45 days per call.

• update_user_lock_days write

  Lock or unlock timesheet days

  Lock days on a user's timesheet so the hours can no longer be edited, or unlock them. Up to 50 dates per call. Cannot reopen an approved payroll period.

• list_schedulers read

  List schedules

  List the account's schedules (rosters), with each one's timezone. Every other schedule call needs an id from here, so read this first.

• list_shifts read

  List shifts

  List shifts on a schedule between two times. Filter by assigned user, job, title, or whether they are open, published or awaiting approval.

• get_shift read

  Get a shift

  Get one shift by id, with its breaks, notes, statuses, custom fields and assigned users.

• create_shifts write

  Create shifts

  Create one or many shifts on a schedule in a single call. New shifts are DRAFTS unless you set isPublished true, and a draft is invisible to staff.

• update_shifts write

  Update shifts

  Update one or many shifts by id. Only the fields you send change. Set notifyUsers false to avoid notifying staff on every published-roster edit.

• delete_shift write

  Delete a shift

  Delete one shift by id. Assigned staff are notified unless you set notifyUsers false.

• delete_shifts write

  Delete shifts

  Delete many shifts at once by id. Use this to clear a draft week in one call rather than one request per shift.

• create_auto_assign_request write

  Auto-assign shifts

  Ask Connecteam to fill open shifts automatically, respecting qualifications, unavailability and approved time off. Returns a request id; processing takes minutes.

• get_auto_assign_status read

  Check auto-assign status

  Check an auto-assign request. Returns which shifts were filled and which could not be, so you can report both.

• get_user_unavailability read

  Check when a user is unavailable

  For one user and time window, return their declared unavailability, approved time off and already-assigned shifts. Read this before rostering someone.

• list_schedule_unavailabilities read

  List unavailability on a schedule

  List declared unavailability on one schedule between two times, across all of its users.

• create_schedule_unavailability write

  Mark a user unavailable

  Mark one user unavailable on a schedule for a whole day, or part of one. Times here are HH:MM:SS strings on a date, not timestamps. Repeats are not supported.

• delete_schedule_unavailability write

  Remove an unavailability

  Delete a declared unavailability from a schedule by its id.

• list_shift_layers read

  List shift layers

  List the extra information layers a schedule attaches to shifts, such as role or department.

• list_shift_layer_values read

  List shift layer values

  List the values a shift layer can take, with their ids. Setting a layer on a shift needs an id from here.

• list_shift_custom_fields read

  List shift custom fields

  List the custom fields a schedule defines on its shifts, including dropdown options and their ids.

• list_task_boards read

  List task boards

  List the account's quick task boards. Every task call needs a board id from here, so read this first.

• list_task_labels read

  List task labels

  List the labels available on a task board. Tagging a task needs a label id from here, not its name.

• list_tasks read

  List tasks

  List quick tasks on a board. Filter by assigned user, label or status. Group tasks are included when filtering by a user in the group.

• create_task write

  Create a task

  Create a quick task on a board. Assigning several users makes ONE group task, not one each. An unassigned task must have status draft.

• update_task write

  Update a task

  Replace a quick task's details. A FULL replace: userIds, status and title are required every time, and anything you leave out is CLEARED — omitting subTasks deletes them all. Read the task first and resend what you want to keep.

• delete_task write

  Delete a task

  Delete a quick task from a board, along with its sub-tasks.

• list_sub_tasks read

  List sub-tasks

  List the sub-tasks under one quick task, with their completion state.

• create_sub_task write

  Add a sub-task

  Add one sub-task to a quick task, without touching the parent's other fields.

• update_sub_task write

  Update a sub-task

  Rename a sub-task or mark it complete. This is the cheapest way to tick one item off without replacing the whole task.

• delete_sub_task write

  Delete a sub-task

  Delete one sub-task from a quick task.

• list_jobs read

  List jobs

  List jobs, the codes the time clock and scheduler attribute hours to. Not to be confused with tasks. Filter by schedule or time clock, name, code or id.

• get_job read

  Get a job

  Get one job by id, with its sub-jobs, assignment, geofence and custom fields. This is the only way to fetch a sub-job directly.

• create_jobs write

  Create jobs

  Create one or many jobs, each attached to at least one schedule or time clock. Sub-jobs can be created inline under a parent.

• update_job write

  Update a job

  Update one job. This REPLACES the whole job: any field you leave out is cleared, so read the job with connecteam_get_job first and send every value you want to keep, not just the ones you are changing. Title is required every time. Connecteam does not support updating a job that has nested sub-jobs.

• delete_job write

  Delete a job

  Delete one job. Connecteam does not support deleting a sub-job, or a job that has sub-jobs. Hours already booked to it stay on the timesheet.

• list_job_custom_fields read

  List job custom fields

  List the custom field definitions available on jobs, with dropdown options and their ids.

• list_forms read

  List forms

  List the account's forms with their questions and settings. Reading submissions needs a form id from here. Filter by name or creation date.

• get_form read

  Get a form

  Get one form by id, with every question, its type and its options. Read this to interpret the answers on a submission.

• list_form_submissions read

  List form submissions

  List submissions for one form, with answers and manager fields. Filter by who submitted and when. This is how you read completed checklists and reports.

• get_form_submission read

  Get a form submission

  Get one submission by id, with its full answers, manager fields, and when the employee started and finished it.

• update_form_submission write

  Update a submission's manager fields

  Set the manager fields on a submission: status, owner, note, date, signature or file. The employee's own answers cannot be changed through this API.

• list_form_dropdown_options read

  List a question's dropdown options

  List the selectable options on a multipleChoice question, with their ids, including ones since deleted. Connecteam's own questions already carry their options, so reach for this when you need deleted options or the list is long.

• list_time_off_policy_types read

  List time off policy types

  List the account's leave types (annual, sick, and so on), each with the individual policies inside it. Every other time off call needs an id from here.

• list_time_off_balances read

  List time off balances

  List how much leave each user has left under one policy type, with the units (hours or days) the policy uses.

• update_time_off_balance write

  Set a user's leave balance

  Set a user's remaining leave under one policy type to an exact figure. This REPLACES the balance rather than adding to it.

• list_time_off_requests read

  List time off requests

  List leave requests overlapping a date range. IMPORTANT: with no statuses filter this returns APPROVED requests only, so pass statuses to see pending ones.

• create_time_off_request write

  Create a time off request

  Book leave for a user. Status approved books it outright and moves their balance; status pending puts it in the approval queue.

• update_time_off_request write

  Approve, deny or change a time off request

  Update a leave request. Setting status to approved is how leave gets approved, and it moves the user's balance. There is no separate approve endpoint.

• assign_user_to_time_off_policy write

  Assign a user to a leave policy

  Put a user on a specific leave policy, optionally seeding their starting balance. Takes a policy id from inside a policy type, not the type id itself.

No tools match your search.