Connecteam MCP Server

Approve timesheets, publish shifts, answer time off and create tasks in Connecteam.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/connecteam'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Connecteam API and MCP server: Let your AI agent close the week in Connecteam.

Connecteam has a REST API on the Expert plan, per hub, and a hosted MCP server whose 3 tools search its API reference (checked 27 Oct 2026). No endpoint approves a timesheet or copies a week. Cotlet runs 14 tools hosted on any paid plan, over MCP for agents and REST for scripts.

Approve timesheets, publish shifts, answer time off and create tasks in Connecteam. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Connecteam. Connecteam is a trademark of its owner. If Connecteam's own integrations cover what you need, use them first.

What can you automate in Connecteam?

  • Approve timesheets by your hours rule
  • Copy last week's schedule
  • Publish shifts that clear time off
  • Answer time off requests
  • Chase missing timesheets
  • Assign Quick Tasks

Does Connecteam have an MCP server or an API?

  • On Expert the API publishes shifts, sets a time off request to approved or denied, creates tasks and sends chat as a custom publisher. Expert costs $99 a month per hub for 30 users, against $29 for Basic and $49 for Advanced, billed yearly.
  • Timesheets come out as totals; approval only shows up as a webhook after someone clicks Approve.
  • Zapier, from Advanced, creates shifts and time off requests and sends messages. It has no action that approves a timesheet or answers a pending request.
What you needAPI (Expert)Zapier (Advanced)Cotlet
Works on Basic and AdvancedExpert onlyAdvanced, not BasicYes, any paid plan
Approve a submitted timesheetNo endpointNoYes, after your OK
Copy last week's shiftsRebuild shift by shiftOne shift per stepYes, one call
Approve or decline time offYesCreate onlyYes, by your rule
Message an employee as youAs a publisherAs a publisherYes, after your OK

Checked 27 Oct 2026. Sources: Connecteam Developer: API access, Connecteam Developer: MCP, Connecteam Developer: Rate limiting, Connecteam pricing, Zapier: Connecteam integrations, Connecteam Help: Zapier integration

How does Cotlet connect to Connecteam?

  1. Sign in to Connecteam. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never see your SMS code or password, and no approval, published shift or message goes out until you confirm it.

Connect Connecteam to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Enable Connecteam for agents. Create a Cotlet account, log in to the Connecteam dashboard in its Cloud Browser with your admin number, and press Enable for agents.
  2. Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in your agent as a remote MCP server or custom connector.
  3. Let the agent in. Chat apps open a Cotlet sign-in window. Editors, n8n and cron scripts send an API key from the console instead.

Connecteam rides on the same https://cotlet.dev/mcp/v1 address as every other app in your workspace. Turned Connecteam on after you connected? Refresh the connector to load its tools.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-connecteam \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-connecteam": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-connecteam]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: connecteam_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: connecteam_write

How to use the Connecteam REST API

Create your Cotlet API key

Create a Cotlet API key with access to Connecteam and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Connecteam in Cotlet and enable it for agents. Account access: Your own Connecteam dashboard login. What your agent can do follows your admin permissions, such as approving timesheets or time off requests.

Make your first Connecteam API request

REST:

curl https://cotlet.dev/api/v1/connecteam/users \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read users and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "connecteam",
  "tool": "list_users",
  "result": {
    "users": [
      {
        "user_id": 8821034,
        "name": "Dana Whitfield",
        "role": "user"
      },
      {
        "user_id": 8821051,
        "name": "Luis Ortega",
        "role": "user"
      },
      {
        "user_id": 8821077,
        "name": "Priya Nair",
        "role": "user"
      }
    ],
    "next_cursor": null
  }
}

Returns the users of your account, one row each, with user_id, name and role. Use user_id in the other tools. status active is the default; archived shows archived users.

Pass next_cursor back as cursor for the next page.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Connecteam workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestTimesheets of a pay period with each employee's submission and approval state and total hours. Use list_timesheets in your configured workspace report.
MakeHTTP > Make a requestShifts of one schedule in a date range, drafts and published, with their assigned users. Use list_shifts in your configured workspace report.
Python or Node.jsREST APITime off requests with employee, policy type, dates and status, pending first. Use list_time_off_requests in your configured workspace report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Connecteam; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Connecteam API endpoints and MCP tools

Time Clock and timesheets

Approval works per time clock, only where Timesheets approval is switched on, and for a whole pay period. Since August 2026 an admin cannot approve their own timesheet.

  • List time clocks (list_time_clocks, read): Time clocks of your account and whether Timesheets approval is on for each.
  • List timesheets (list_timesheets, read): Timesheets of a pay period with each employee's submission and approval state and total hours.
  • Get a timesheet (get_timesheet, read): One employee's timesheet day by day, with clock in, clock out, hours and locked days.
  • Approve a timesheet (approve_timesheet, write, asks first): Approve one employee's submitted timesheet for a pay period. Your account needs approve permission.

Job Scheduler

Copied shifts land as drafts. Publishing only some drafts is an Advanced bulk action; a shift needs a title or job and an assignee or claiming to publish.

  • List schedules (list_schedulers, read): The schedules of your Job Scheduler with their IDs and names.
  • List shifts (list_shifts, read): Shifts of one schedule in a date range, drafts and published, with their assigned users.
  • Copy the previous week (copy_previous_week, write, asks first): Copy every shift of the previous week into the week you name, as drafts, or only one employee's shifts.
  • Publish shifts (publish_shifts, write, asks first): Publish the draft shifts of a schedule so employees see them. All drafts, or only the shift ids you pass.

Time Off

Needs the HR & Skills hub with admin approval on. The agent sees the requests of people you manage or whose smart group you run.

  • List time off requests (list_time_off_requests, read): Time off requests with employee, policy type, dates and status, pending first.
  • Approve or decline time off (decide_time_off_request, write, asks first): Approve or decline one pending time off request. Your account must be allowed to act on that employee.

Users, Quick Tasks and Chat

Messages go out from your own admin profile, text only, and cannot be recalled.

  • List users (list_users, read): Employees and admins of your Connecteam account with their user IDs.
  • List tasks (list_tasks, read): Quick Tasks with title, assignees, due date and whether they are done.
  • Create a task (create_task, write, asks first): Create and publish a Quick Task for one or more users, with a title, optional description and due date.
  • Send a chat message (send_message, write, asks first): Send a private message to one user in Connecteam Chat.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/connecteam-api-mcp-server#tools

Who can see my Connecteam session, and how do I revoke it?

  • What we store. Your logged-in Connecteam profile, AES-256-GCM, kept in Finland. No SMS code, no password.
  • What your agent gets. The 14 Connecteam tools. Never the session cookie.
  • What the session sees. What your admin role sees: hours, shifts, time off and chats of your team.
  • What no tool touches. Payroll export, pay rates, billing, user records and account settings.
  • If Connecteam asks again. A new SMS code or 2FA PIN goes to your phone. You enter it, we never do.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call is refused.

Qualys SSL Labs, securityheaders.com and Mozilla Observatory grade our site A+ (live results).

Approvals, undo and mistakes

  1. Reads the pay period. Submitted and missing timesheets for one time clock.
  2. Checks each day. Hours against your rule, quoting the day that breaks it.
  3. Waits for your OK. Each approval appears in your Cotlet console first.
  4. Reports the rest. Held timesheets and who never submitted, one line each.
ActionUndo
Approve a timesheetAn admin with reopen permission reopens it
Copy previous weekDrafts only; delete them in the scheduler
Publish shiftsUnpublish in the scheduler; the push already went out
Approve or decline time offChange it in the request's History tab
Send a chat messageNo, this tool cannot recall it

All 6 write tools ask first, since each one reaches an employee or locks in hours for payroll. The 8 reads run at once. Switch the wait off per tool once a weekly run has earned it.

A closed pay period needs the Payroll Manager permission to reopen, which no tool uses. Approve before you close the period.

MCP call:

{
  "name": "approve_timesheet",
  "arguments": {
    "time_clock_id": 2041,
    "user_id": 8821034,
    "period_start": "2026-10-12",
    "period_end": "2026-10-18"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/connecteam/time-clocks/2041/timesheet/approve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"user_id":8821034,"period_start":"2026-10-12","period_end":"2026-10-18"}'

Response:

{
  "approved": true,
  "time_clock_id": 2041,
  "user_id": 8821034,
  "name": "Dana Whitfield",
  "period_start": "2026-10-12",
  "period_end": "2026-10-18",
  "total_hours": 38.5
}

Cron jobs and scripts call the same tools over REST at /api/v1/connecteam, with one key and one price. A call your admin role may not make, such as approving on a time clock where you are not an approver, fails with APP_PERMISSION_DENIED and costs nothing. The tools table shows each REST path.

How much does the Connecteam MCP server cost?

About $24 a month for a 20-person team on a weekly pay period, 4,220 credits. Connecteam keeps billing your plan as before.

JobCallsCredits
Check and approve 18 timesheets, weekly36 × 41,440
Copy, check and publish the week5 × 4200
Read the time off queue, daily2 × 30600
Approve or decline a time off request1 × 880
Chase missing timesheets, weekly4 × 4160
Create and assign a task2 × 12240
Cloud Browser, 30 days1,500
Total4,220
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No Expert upgrade, which adds $50 a month per hub

The team size is our example: Connecteam counts 80,000+ companies and 1.2 to 1.8 million users, about 15 to 23 each, and prices every plan for the first 30 users. The weekly pass reads each timesheet before approving it. Dollars at the $29 pack rate.

Connecteam MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Connecteam docs MCPOfficial, free: list, get and search the API endpoints from your editor.Three doc tools; nothing reads or changes your account.
Composio and mcp.aiHosted MCP, 16 tools: users, schedules, task boards, forms, chat, jobs.Your Expert API key; no shift, time off or timesheet writes in the list.
Pipedream MCPHosted MCP on the Connecteam app in Pipedream.Same API, so Expert and no timesheet approval.
Zapier MCPZapier's Connecteam actions as MCP tools, 2 Zapier tasks per call.Advanced or higher; creates shifts and requests, approves nothing.
GitHubNo Connecteam MCP server; Jarvis0p/connectcli, a small CLI (2 stars, last commit 11 May 2026).Yours to run and keep working.

On Expert with a developer around, the official API is the safer route for publishing shifts and deciding time off. If you are on Basic or Advanced, or the job is approving timesheets and copying the week, Cotlet does it in the dashboard you already use.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Connecteam tools go to contact@cotlet.dev.

Connecteam API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Connecteam under Integrations in the console and log in to the dashboard in its Cloud Browser with your admin number. The trial starts when you sign up, no card asked.

How do I connect Connecteam to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Connecteam once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Connecteam account through Cotlet, in their phone apps too.

What can ChatGPT do in Connecteam?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Connecteam: approve submitted timesheets; copy last week; approve or decline time off requests. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need the Expert plan or an API key?

No. Cotlet works in your own Connecteam dashboard login, so it does not use the API, which starts at the Expert plan. Your admin permissions still count: approving a timesheet needs an admin chosen in the time clock's Payroll settings, and acting on time off needs a user you manage or whose smart group you administer. A call without the permission fails with APP_PERMISSION_DENIED.

Which tools need which Connecteam hub?

A tool works where your account has the feature. Time clock, schedules and Quick Tasks belong to the Operations hub, time off to HR & Skills and chat to Communications. Publishing only some drafts is a bulk action of the Advanced plan, and time off approval needs the HR Basic plan or higher.

Does Connecteam have webhooks?

Yes, on Expert: time activities, shifts, tasks, chat, form submissions and timesheet events such as submitted and approved. Cotlet does not use them. On a lower plan, run your agent on a schedule instead, for example every Monday after the pay period closes.

Does it work on the free Small Business plan?

Yes, as long as your login is an admin with the feature switched on. Cotlet works in the dashboard on any plan; Connecteam's own limits per plan stay, such as how many time clocks and schedules you have.

Who does an employee see as the sender?

You. send_message posts from your own admin profile, the way you would from the Chat icon. The API, by contrast, sends as a custom publisher.

Is the MCP server different from the REST API?

Only in how you call it. Both carry the same 14 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Connecteam?

No. Cotlet is independent and not affiliated with Connecteam.

Can I use the Connecteam API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.