How to Connect Connecteam to Gemini via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Connecteam, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Connecteam + Gemini

Connecteam, the workforce app for deskless teams: users and custom fields, the time clock with clocked shifts, timesheet totals and clock in and out, scheduler shifts, jobs, forms and submissions, quick tasks, time off balances and requests, and chat messages. Connecteam API with an API key.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CONNECTEAM_API_HOST, CONNECTEAM_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes and needs a Connecteam owner or admin.

1. In Connecteam open Settings > API Keys and click Add API key. Copy the key into CONNECTEAM_API_KEY. It gives access to the whole account, so treat it like a password.
2. Set CONNECTEAM_API_HOST to https://api.connecteam.com, or to https://api-au.connecteam.com if you sign in at app-au.connecteam.com (Australian accounts).
3. Install the connector: connecteam_get_account is the install check.

API access needs the Expert plan or higher, per hub: Operations for the time clock, scheduler, jobs and tasks; Communications for chat; HR & Skills for time off. Users, the account and publishers work with any eligible hub.

Personal data: users carry names, phone numbers, emails and custom profile fields such as birthday, address or ID numbers; time activities can carry GPS positions. Ask only for what the task needs.

Ids first: every time clock, scheduler and task board is its own app instance. The AI gets their ids with connecteam_list_time_clocks, connecteam_list_schedulers and connecteam_list_task_boards before it calls the tools that need timeClockId, schedulerId or taskBoardId.

What it reads:

• Account and people: connecteam_get_account, connecteam_list_users (filter by ids, names, emails, phones, status or change time), connecteam_list_custom_fields, connecteam_list_custom_field_categories and connecteam_list_smart_groups.
• Time clock: connecteam_list_time_activities returns clocked shifts, manual breaks and time off per user, at most 92 days per call; connecteam_get_timesheet_totals returns hours per user and day with breaks, overtime, pay and approval, submission and lock state.
• Scheduling: connecteam_list_shifts (time range in Unix seconds), connecteam_get_shift, connecteam_list_shift_custom_fields and connecteam_list_user_unavailabilities.
• Jobs (the clients, sites or projects that shifts and clocked time are tracked against): connecteam_list_jobs, connecteam_get_job and connecteam_list_job_custom_fields.
• Forms: connecteam_list_forms, connecteam_get_form (the questions), connecteam_list_form_submissions and connecteam_get_form_submission with every answer, including images and file links.
• Tasks: connecteam_list_tasks and connecteam_list_task_labels.
• Time off: connecteam_list_time_off_policy_types, connecteam_list_time_off_balances and connecteam_list_time_off_requests, which returns approved requests only unless you pass statuses.
• Chat: connecteam_list_conversations and connecteam_list_publishers.

What it writes:

• Time clock: connecteam_clock_in and connecteam_clock_out punch a user now or at a timestamp, optionally on a job or a scheduled shift. connecteam_create_time_activities adds past shifts or manual breaks (for example a forgotten clock-in) and connecteam_update_time_activities corrects them. Locked or approved days are refused.
• Scheduling: connecteam_create_shifts and connecteam_update_shifts; with isPublished true and notifyUsers true the staff see the shift and are told about it.
• Jobs: connecteam_create_jobs (also sub-jobs with parentId) and connecteam_update_job (title is required).
• Tasks: connecteam_create_task and connecteam_update_task. The API replaces the whole task, so the AI sends userIds, status and title every time; status completed closes it.
• Time off: connecteam_create_time_off_request (pending or already approved) and connecteam_update_time_off_request (approve or deny with status).
• Users: connecteam_create_users (each needs firstName, lastName, phoneNumber and userType; sendActivation sends the activation SMS), connecteam_update_users, connecteam_archive_users (reversible: update with isArchived false) and connecteam_create_user_note.
• Chat: connecteam_send_message posts to a conversation and connecteam_send_private_message writes to one user, both with a publisher id from connecteam_list_publishers as senderId. Messages are delivered at once.

Switched off at install: connecteam_delete_user, connecteam_delete_shift and connecteam_delete_task. They cannot be undone; a workspace admin switches them on when the team needs them. Archiving a user is the reversible alternative.

Data formats: answers look like { "requestId": "...", "data": {...}, "paging": { "offset": n } }. Shift, clock and task times are Unix timestamps in seconds with a separate IANA timezone; dates in filters are YYYY-MM-DD. User ids are integers; shift, job, task and request ids are strings. Batch writes (connecteam_create_users, connecteam_create_shifts, connecteam_create_jobs and the updates) take a list and answer per item.

Paging: limit (default 10; the maximum depends on the tool, up to 500) and offset. The AI raises offset by limit until a page returns fewer items than limit.

Limits and common errors: rate limits are per account and plan (Expert: 100 requests per minute and 10,000 per day) and answer 429. 401 or 403 means a wrong key, the wrong API address (global versus Australian) or a plan or hub without API access; 404 an unknown id; 422 a validation error, with the field named in the body.

The connector does not run payroll, does not edit forms or submit form answers, and does not create time clocks, schedulers or task boards.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell): anythingmcp should show as connected.
4. Start prompting: Gemini CLI can now call the Connecteam tools.

Available tools

Example prompts

• "How many hours did each employee work last week on the Warehouse time clock, including overtime?"
• "Show tomorrow's open shifts in the Field Team scheduler."
• "Which time off requests are still pending, and how much balance does each person have left?"
• "List this week's submissions of the vehicle inspection form with their answers."
• "Create a task for Daniel on the Store board to restock the cold room by Friday and publish it."

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Meta Muse
• Connect to Microsoft Copilot