Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"connecteam": {
"url": "https://connecteam.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"connecteam": {
"type": "http",
"url": "https://connecteam.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Connecteam API key and Data region.
Create one in Connecteam → Settings → API Keys (an owner or admin can; the API needs the Expert plan or higher). Pick Australia only if you sign in at app-au.connecteam.com. Your key is used only to call the Connecteam API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Connecteam API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Connecteam connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
connecteam_get_account | read | Get account The Connecteam company this API key belongs to: company name and company id. GET /me. |
connecteam_list_users | read | 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. |
connecteam_list_schedulers | read | 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 | read | 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. |
connecteam_get_shift | read | Get shift One shift of a scheduler by its id, with assignments, statuses, breaks, notes and tasks. GET /scheduler/v1/schedulers/{schedulerId}/shifts/{shiftId}. |
connecteam_create_shift | write | 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. |
connecteam_list_time_clocks | read | 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 | read | 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. |
connecteam_get_timesheet_totals | read | 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. |
connecteam_list_jobs | read | 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. |
connecteam_get_job | read | Get job One job by id, with its sub-jobs, assignments and location. GET /jobs/v1/jobs/{jobId}. |
connecteam_list_time_off_policy_types | read | 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 | read | 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. |
connecteam_list_task_boards | read | 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 | read | 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. |
connecteam_list_task_labels | read | 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. |
connecteam_create_task | write | 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. |
connecteam_list_forms | read | List forms List forms (checklists, inspections, reports) with their questions. Filter by name or creation date. GET /forms/v1/forms. |
connecteam_list_form_submissions | read | 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. |
connecteam_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
connecteam_request_feature | Request a missing feature Tell usefulapi that the user needs something the Connecteam tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
connecteam_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Connecteam (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
connecteam_cancel_subscription | Cancel the Pro subscription Cancel the caller's Connecteam Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run connecteam_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper company | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Connecteam server only. Subscribe with connecteam_upgrade (it returns a Stripe Checkout link). Cancel any time with connecteam_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running connecteam_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Connecteam. The server calls the Connecteam API with your own Connecteam access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Connecteam API key and Data region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Connecteam API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Connecteam API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Connecteam.
Yes, if you approve it. 2 of the 19 Connecteam tools can create or change data. The other 17 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Connecteam server only. Cancel any time: Pro then runs to the end of the paid period. Run connecteam_usage_status to see how many calls you used.
Ask the AI to run connecteam_upgrade: it returns a Stripe Checkout link. To cancel, run connecteam_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with connecteam_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.