# Connecteam MCP by usefulapi (remote · connecteam.usefulapi.io)

Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks.

- Trust score: 65/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `connecteam.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam.md), [page](https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam)

## Channel facts

- Endpoint: `https://connecteam.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3286 tokens (~172/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Connecteam MCP by usefulapi server?

Connecteam MCP by usefulapi is a hosted endpoint at https://connecteam.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-connecteam 'https://connecteam.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-connecteam": {
      "url": "https://connecteam.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-connecteam": {
      "type": "http",
      "url": "https://connecteam.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-connecteam]
url = "https://connecteam.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-connecteam": {
      "type": "remote",
      "url": "https://connecteam.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-connecteam --url 'https://connecteam.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-connecteam:
    url: "https://connecteam.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-connecteam": {
      "Transport": "http",
      "Url": "https://connecteam.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-connecteam -t streamable-http -u 'https://connecteam.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-connecteam": {
      "type": "http",
      "url": "https://connecteam.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.4.0 → 1.5.0

### 2026-10-12 (score 61, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 60)

First indexed and scored.

## MCP tools (19)

### `connecteam_get_account` (~30 tokens)

Get account

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

### `connecteam_list_users` (~248 tokens)

List users

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.

Input parameters:

- `emails` (array): Exact email addresses.
- `full_names` (array): Exact full names ('First Last', case-insensitive).
- `limit` (integer): Results per page, 1-100 (default 25).
- `modified_since`: Only users changed after this time (Unix seconds or ISO 8601 date-time with zone).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `order` (string): Sort order (only with a sort key).
- `phone_numbers` (array): Phone numbers in +<country code><number> format.
- `sort` (string): Sort key.
- `status` (string): User status filter (Connecteam default: active).
- `user_ids` (array): Only these user ids.

### `connecteam_list_schedulers` (~54 tokens)

List schedulers

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.

### `connecteam_list_shifts` (~314 tokens)

List shifts

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.

Input parameters:

- `assigned_user_ids` (array): Only shifts assigned to these user ids.
- `end_time` (required): Window end: Unix seconds or ISO 8601 date-time with zone.
- `is_open_shift` (boolean): true = only open shifts, false = only assigned shifts.
- `is_published` (boolean): true = only published shifts, false = only drafts.
- `job_ids` (array): Only shifts of these job ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `order` (string): Sort order (only with a sort key).
- `scheduler_id` (integer, required): Scheduler id (connecteam_list_schedulers).
- `shift_ids` (array): Only these shift ids.
- `sort` (string): Sort key.
- `start_time` (required): Window start: Unix seconds or ISO 8601 date-time with zone.
- `title` (string): Only shifts with this title.

### `connecteam_get_shift` (~74 tokens)

Get shift

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

Input parameters:

- `scheduler_id` (integer, required): Scheduler id.
- `shift_id` (string, required): Shift id (from connecteam_list_shifts).

### `connecteam_create_shift` (~415 tokens)

Create shift

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_shift=true and leave assigned_user_ids empty. POST /scheduler/v1/schedulers/{schedulerId}/shifts.

Input parameters:

- `assigned_user_ids` (array): The user id to assign (at most one: the V1 endpoint rejects more); empty for an open shift.
- `color` (string): Shift color from Connecteam's palette; defaults to the job's color (or #4B7AC5).
- `end_time` (required): Shift end: Unix seconds or ISO 8601 date-time with zone.
- `is_open_shift` (boolean): Create an open shift with one spot that an employee can claim (default false).
- `is_published` (boolean): Publish the shift now (default false = draft).
- `job_id` (string): Job id (connecteam_list_jobs) to attach the shift to.
- `note` (string): A plain-text note shown on the shift.
- `notify_users` (boolean): For a published shift: notify the assigned users (Connecteam default true).
- `require_admin_approval` (boolean): Claiming needs admin approval (open shifts only).
- `scheduler_id` (integer, required): Scheduler id (connecteam_list_schedulers).
- `start_time` (required): Shift start: Unix seconds or ISO 8601 date-time with zone.
- `task_titles` (array): Shift tasks (checklist items) by title.
- `timezone` (string): IANA time zone, e.g. America/New_York (default: the account's time zone).
- `title` (string): Shift title (required unless job_id is given).

### `connecteam_list_time_clocks` (~49 tokens)

List time clocks

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.

### `connecteam_list_time_activities` (~191 tokens)

List time activities

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.

Input parameters:

- `activity_types` (array): Only these activity types.
- `end_date` (string, required): Last date (yyyy-mm-dd), at most 31 days after start_date.
- `job_ids` (array): Only shifts of these job ids.
- `start_date` (string, required): First date (yyyy-mm-dd).
- `time_clock_id` (integer, required): Time clock id (connecteam_list_time_clocks).
- `user_ids` (array): Only these user ids (users still assigned to the time clock).

### `connecteam_get_timesheet_totals` (~297 tokens)

Get timesheet totals

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.

Input parameters:

- `end_date` (string, required): Last date (yyyy-mm-dd), up to 23:59:59; at most 45 days after start_date.
- `group_ids` (array): Only users in these smart group ids.
- `include_plan_vs_actual` (boolean): Add scheduled-vs-actual details per day (default false).
- `is_approved` (boolean): true = approved days only, false = unapproved only.
- `is_locked` (boolean): true = locked only, false = unlocked only.
- `is_submitted` (boolean): true = submitted only, false = unsubmitted only.
- `job_ids` (array): Only these (parent or regular) job ids.
- `start_date` (string, required): First date (yyyy-mm-dd), from 00:00:00.
- `time_clock_id` (integer, required): Time clock id (connecteam_list_time_clocks).
- `user_ids` (array): Only these user ids.

### `connecteam_list_jobs` (~218 tokens)

List jobs

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.

Input parameters:

- `include_deleted` (boolean): Include deleted jobs (Connecteam default: true).
- `instance_ids` (array): Only jobs of these scheduler or time clock ids.
- `job_codes` (array): Only jobs with these codes.
- `job_ids` (array): Only these job ids (a parent id also returns its sub-jobs).
- `job_names` (array): Only jobs with these titles.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `order` (string): Sort order (only with a sort key).
- `sort` (string): Sort key.

### `connecteam_get_job` (~51 tokens)

Get job

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

Input parameters:

- `job_id` (string, required): Job id (from connecteam_list_jobs).

### `connecteam_list_time_off_policy_types` (~58 tokens)

List time-off policy types

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.

### `connecteam_list_time_off_requests` (~202 tokens)

List time-off requests

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.

Input parameters:

- `end_date` (string, required): Range end (yyyy-mm-dd), inclusive; at most 365 days after start_date.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `start_date` (string, required): Range start (yyyy-mm-dd), inclusive.
- `statuses` (array): Statuses to include (default: approved only).
- `user_ids` (array): Only these user ids.

### `connecteam_list_task_boards` (~46 tokens)

List task boards

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.

### `connecteam_list_tasks` (~192 tokens)

List tasks

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.

Input parameters:

- `label_ids` (array): Only tasks carrying these label ids.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `status` (string): Status filter (default all).
- `task_board_id` (string, required): Task board id (connecteam_list_task_boards).
- `task_ids` (array): Only these task ids.
- `user_ids` (array): Only tasks assigned to these user ids (group tasks are included).

### `connecteam_list_task_labels` (~117 tokens)

List task labels

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

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `task_board_id` (string, required): Task board id.
- `title` (string): Only the label with this name.

### `connecteam_create_task` (~219 tokens)

Create task

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.

Input parameters:

- `description` (string): Task description (plain text).
- `due_date`: Due: Unix seconds or ISO 8601 date-time with zone.
- `label_ids` (array): Label ids (connecteam_list_task_labels).
- `start_time`: Start: Unix seconds or ISO 8601 date-time with zone.
- `status` (string, required): 'draft' (not visible to employees) or 'published' (sent to the assignees).
- `sub_tasks` (array): Sub-task titles.
- `task_board_id` (string, required): Task board id (connecteam_list_task_boards).
- `title` (string, required): Task title.
- `user_ids` (array, required): Assignee user ids (several = one group task).

### `connecteam_list_forms` (~126 tokens)

List forms

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

Input parameters:

- `created_from` (string): Created on or after (yyyy-mm-dd).
- `created_to` (string): Created on or before (yyyy-mm-dd).
- `limit` (integer): Results per page, 1-100 (default 25).
- `name` (string): Name contains (case-insensitive).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.

### `connecteam_list_form_submissions` (~175 tokens)

List form submissions

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.

Input parameters:

- `form_id` (integer, required): Form id (connecteam_list_forms).
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Index of the first result (default 0); pass the previous reply's next_offset.
- `submitted_from`: Submitted at or after: Unix seconds or ISO 8601 date-time with zone.
- `submitted_to`: Submitted at or before: Unix seconds or ISO 8601 date-time with zone.
- `user_ids` (array): Only submissions by these user ids.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 61
- 2026-10-10: 60

## Common questions

### What is the Connecteam MCP by usefulapi server?

Connecteam MCP by usefulapi is listed in the public MCP registry as io.usefulapi/connecteam. Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks. This page covers its hosted endpoint (https://connecteam.usefulapi.io/mcp).

### Is the Connecteam MCP by usefulapi server safe to use?

Connecteam MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Connecteam MCP by usefulapi server expose?

Connecteam MCP by usefulapi exposes 19 tools: connecteam_get_account, connecteam_list_users, connecteam_list_schedulers, connecteam_list_shifts, connecteam_get_shift, and 14 more. Their descriptions and schemas cost roughly 3,076 tokens of context every time the server is loaded.

### Does the Connecteam MCP by usefulapi server require authentication?

Yes. Connecteam MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Connecteam MCP by usefulapi server still maintained?

Connecteam MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://connecteam.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/connecteam/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-connecteam/connecteam