Connecteam

@Connecteam list all custom fields in our account, grouped by category, so I can see what employee data we're tracking.

Here's an illustrative summary of custom fields in your Connecteam account: **HR & Onboarding** (5 fields): Emergency Contact Name, Emergency Contact Phone, T-Shirt Size, Dietary Restrictions, Start Date. **Certifications** (3 fields): Forklift License Expiry, Food Handler Cert Number, CPR Training Date. **Payroll** (2 fields): Bank Account Number, Tax Filing Status. This example shows how the MCP retrieves structured employee metadata; actual field names and categories depend on your account configuration.

This example demonstrates read-only access to your custom field schema. Requires API key with read permissions for user data. Useful for auditing what employee attributes you're collecting before building workflows that reference these fields.

@Connecteam create three new users: John Doe (john@example.com, admin role), Sarah Lee (sarah@example.com, staff), and Mike Chen (mike@example.com, staff).

Created 3 users successfully: John Doe (ID: usr_8x7k2m, admin), Sarah Lee (ID: usr_9p4n1q, staff), Mike Chen (ID: usr_3r6t8w, staff). All accounts are active and invitation emails have been sent to their respective addresses. This illustrative response shows the MCP's batch user creation; actual user IDs and email delivery depend on your account settings and email configuration.

This write operation immediately provisions accounts and triggers invitation emails. Requires API key with user management permissions. Be cautious with bulk creation—typos in email addresses or role assignments can't be undone without manual cleanup or archiving users.

@Connecteam pull all open jobs from our scheduler for the next 7 days and summarize which roles have the most unfilled shifts.

Analyzing 47 scheduled jobs from your Time Clock instance (ID: inst_5k2m): **Warehouse Associate** has 12 unfilled shifts (Mon-Fri mornings), **Delivery Driver** has 8 gaps (Wed-Sat evenings), **Customer Service** has 3 openings (weekend afternoons). Most critical shortage is Warehouse Associate on Thursday 9am-5pm with zero assigned staff. This example illustrates how the MCP fetches job data and the AI synthesizes staffing gaps; actual job counts and role names reflect your scheduler configuration.

This synthesis example pairs the Get Jobs tool with AI reasoning to surface staffing risks. Requires your scheduler or time clock instance ID and API access to job data. Rate limits may apply if you're querying large date ranges or multiple locations.

When Connecteam MCP handles bulk seasonal hiring

A 12-person retail chain hiring 40 seasonal workers for holiday rush needs to create accounts, assign custom fields for location and shift preference, and archive them post-season. The Connecteam MCP wins here because Create Users and Archive Users handle batch operations in one call, and Get Custom Fields lets you validate location codes before assignment. The trade-off: if your onboarding includes document signing or training modules, you'll still need Connecteam's web UI for those workflows—this MCP only covers user provisioning and metadata. Use this when your seasonal hiring spikes above 20 people per quarter and you're tired of manual CSV imports.

When chat retrieval fits distributed team ops

A 6-person facilities management company with 30 field techs uses Connecteam for daily check-ins and incident reports. The operations manager wants to pull yesterday's chat threads into a standup summary without opening the mobile app. Get Chat works if you're on Connecteam's Expert plan and your comms hub is enabled—otherwise the tool returns empty. The MCP shines for low-frequency audits (weekly summaries, monthly compliance checks) but falls short if you need real-time alerting or message search across date ranges. If your team sends under 50 messages per day and you're already paying for Expert, this is a clean fit for end-of-week reporting.

When form retrieval supports safety documentation

A 20-person construction firm runs daily safety checklists and incident forms across four active sites. The safety officer needs to verify which forms are deployed and pull submission counts for quarterly audits. Get Forms retrieves all form definitions after you enable the forms API in Connecteam settings, and you can cross-reference with Get Jobs to see which sites are using which templates. The limitation: this MCP doesn't fetch form submissions or attachments—only the form structure. Use this when you need to audit form coverage or clone templates across projects, not when you're investigating a specific incident that requires submission data.