How to Connect Crewmeister to Gemini — via MCP

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

Crewmeister + Gemini

Crewmeister, German time tracking, absence planning and shift planning for small businesses: members, teams and roles, absences and leave balances, clock stamps, durations, overtime balances, working time models, shifts, templates and workplaces. API v3 with a login token.

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:

CREWMEISTER_EMAIL, CREWMEISTER_PASSWORD

Step 1 — Get credentials

The connector signs in to Crewmeister API v3 with the e-mail address and password of a Crewmeister user, receives a token and logs in again on its own when it expires. It sees exactly what that user may see.

1. Pick or create a Crewmeister user with an e-mail and password login for the integration. Single sign-on accounts without a Crewmeister password cannot log in. Use a crew owner or manager account for company-wide data; an ordinary member sees only their own records.
2. Put the login e-mail into CREWMEISTER_EMAIL and the password into CREWMEISTER_PASSWORD. Check first that the same pair signs in at app.crewmeister.com.
3. Start with crewmeister_list_members for each person's userId and crewmeister_list_crews for the crewId, then crewmeister_list_absence_types to map absence type ids to names.

Things to know:

• Some tools answer 400 without fixed filters: 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>.
• Filters are RSQL, for example userId==123;date=ge=2026-09-01;date=le=2026-09-30. Pages start at 0 and hold 20 items by default.
• For hours worked use durations, for who is clocked in now use today's stamps, and for remaining vacation use crewmeister_list_entitlement_balances.
• The crew's join password and members' terminal PIN codes are removed from the answers. The connector uses API v3 only; v2 was retired on 31 March 2026.

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 Crewmeister tools.

Available tools

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