Crewmeister

Credentials: Crewmeister API v3 signs in with the e-mail address and password of a Crewmeister user. AnythingMCP posts them to /api/v3/auth/user/, receives a JWT and sends it as Authorization: Bearer on every call; it logs in again on its own when the token expires. Use a dedicated user (for example an admin account created for the integration) rather than a personal one: the API returns exactly what that user may see, so an ordinary member sees only their own data, while a crew owner or manager sees the whole crew or their teams. Single sign-on accounts without a Crewmeister password cannot log in here.

Where to start: crewmeister_list_members gives every person's userId (the id all other tools filter on) and crewmeister_list_crews the crewId. Then crewmeister_list_absence_types maps absence type ids to names.

Mandatory filters: five resources are computed per crew and date and answer 400 without them: crewmeister_list_durations and crewmeister_list_calendar_days need crewId==<id> plus a date or date range, crewmeister_list_duration_balances and crewmeister_list_entitlement_balances need crewId==<id>;date==<day>, and crewmeister_list_absence_entitlements needs crewId==<id>. Ranges such as crewId=gt=0 are not accepted there.

Filtering (RSQL): every list tool takes filter, an RSQL expression. Use ==, !=, =lt=, =le=, =gt=, =ge=, =in=(1,2); join conditions with ; (AND) or , (OR); * is a wildcard in string values. Examples: userId==123;date=ge=2026-09-01;date=le=2026-09-30 for one person's month, state==REQUESTED for open absence requests. Dates are yyyy-MM-dd; timestamps are ISO 8601 with an offset. A filter on a field the resource does not support answers 400 INVALID_ARGUMENT.

Paging: pages start at 0 and hold 20 items by default (page_size to change). The answer has content, totalElements, totalPages and hasNextPage; call again with page + 1 while hasNextPage is true. sort takes keys such as +from or -timestamp.

Which time data to use: stamps are the raw clock-in and clock-out events, bookings are the processed time entries, durations the per-day totals by type (WORK, BREAK, OVERTIME), and duration balances the running overtime account. For "hours worked last month" use durations; for "who is clocked in now" use stamps of today.

Absences move through DRAFT, REQUESTED, PRE_APPROVED, APPROVED, REJECTED and REVOKED. Remaining vacation is in crewmeister_list_entitlement_balances (filter userId and a date).

Secrets are left out: the crew's join password and members' terminal PIN codes are removed from the answers.

Errors: 401 means the login failed or the token was refused; 403 PERMISSION_DENIED and 404 NOT_FOUND also cover records the user may not see. Reading with a filter the user may not see returns an empty page rather than an error.

The v2 API was retired on 31 March 2026; this connector uses v3 only.