[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Connecteam MCP tools

> The Connecteam MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/connecteam

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Connecteam has 14 operations on the Cotlet MCP server, in connecteam_read and connecteam_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `connecteam_read`, `connecteam_write`
- Connects with: Your own Connecteam dashboard login. What your agent can do follows your admin permissions, such as approving timesheets or time off requests.
- Integration page: https://cotlet.dev/integrations/connecteam-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_users`](https://cotlet.dev/docs/mcp/connecteam/list_users.md) | Employees and admins of your Connecteam account with their user IDs. |
| [`list_time_clocks`](https://cotlet.dev/docs/mcp/connecteam/list_time_clocks.md) | Time clocks of your account and whether Timesheets approval is on for each. |
| [`list_timesheets`](https://cotlet.dev/docs/mcp/connecteam/list_timesheets.md) | Timesheets of a pay period with each employee's submission and approval state and total hours. |
| [`get_timesheet`](https://cotlet.dev/docs/mcp/connecteam/get_timesheet.md) | One employee's timesheet day by day, with clock in, clock out, hours and locked days. |
| [`list_schedulers`](https://cotlet.dev/docs/mcp/connecteam/list_schedulers.md) | The schedules of your Job Scheduler with their IDs and names. |
| [`list_shifts`](https://cotlet.dev/docs/mcp/connecteam/list_shifts.md) | Shifts of one schedule in a date range, drafts and published, with their assigned users. |
| [`list_time_off_requests`](https://cotlet.dev/docs/mcp/connecteam/list_time_off_requests.md) | Time off requests with employee, policy type, dates and status, pending first. |
| [`list_tasks`](https://cotlet.dev/docs/mcp/connecteam/list_tasks.md) | Quick Tasks with title, assignees, due date and whether they are done. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`approve_timesheet`](https://cotlet.dev/docs/mcp/connecteam/approve_timesheet.md) (Confirm) | Approve one employee's submitted timesheet for a pay period. Your account needs approve permission. |
| [`copy_previous_week`](https://cotlet.dev/docs/mcp/connecteam/copy_previous_week.md) (Confirm) | Copy every shift of the previous week into the week you name, as drafts, or only one employee's shifts. |
| [`publish_shifts`](https://cotlet.dev/docs/mcp/connecteam/publish_shifts.md) (Confirm) | Publish the draft shifts of a schedule so employees see them. All drafts, or only the shift ids you pass. |
| [`decide_time_off_request`](https://cotlet.dev/docs/mcp/connecteam/decide_time_off_request.md) (Confirm) | Approve or decline one pending time off request. Your account must be allowed to act on that employee. |
| [`create_task`](https://cotlet.dev/docs/mcp/connecteam/create_task.md) (Confirm) | Create and publish a Quick Task for one or more users, with a title, optional description and due date. |
| [`send_message`](https://cotlet.dev/docs/mcp/connecteam/send_message.md) (Confirm) | Send a private message to one user in Connecteam Chat. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.
