ZenSched — field workforce scheduling for agents

Agent-first field workforce scheduling.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Zensched Guide: START HERE. The ZenSched agent guide: how to Connect (Claude.ai) or use a zsc_ key, then fund → locations → workers → shifts → timesheets. Also covers the suggestion box (feedback_subm
  • Feedback Submit: File a grievance or product recommendation. Free. Works even before you have an account. Categories: bug, friction, missing_capability, docs, billing, feature, other. Severity: low, m
  • Account Create: Create a ZenSched org without email (MCP-only agents). No OTP — returns org_id + zsc_ key immediately. Store the key securely. To attach a contact email later for human recovery, call

What data it sees

Do you need an account

No: the server works without sign-in

Agent-first field workforce scheduling. Your agent schedules crews, verifies GPS punches, collects forms, and exports timesheets. No dashboard. Keys zsc_. $5 activation credited. Worker invite $0.25. No seats. Docs: https://www.zensched.com/docs/quickstart/ Pricing: https://www.zensched.com/pricing/ Android: https://play.google.com/store/apps/details?id=com.zensched.app iOS: https://apps.apple.com/us/app/zensched/id6800081657

Server tool list (11)

Raw names from tools/list. Only developers need these.

zensched_guideSTART HERE. The ZenSched agent guide: how to Connect (Claude.ai) or use a zsc_ key, then fund → locations → workers → shifts → timesheets. Also covers the suggestion box (feedback_submit).
feedback_submitFile a grievance or product recommendation. Free. Works even before you have an account. Categories: bug, friction, missing_capability, docs, billing, feature, other. Severity: low, medium, high, blocker. Include related_tool and paste error text in context when reporting a bug. A human reads every submission.
account_createCreate a ZenSched org without email (MCP-only agents). No OTP — returns org_id + zsc_ key immediately. Store the key securely. To attach a contact email later for human recovery, call account_set_contact. Rate-limited aggressively.
account_signup_startCreate a ZenSched org (step 1 of 2): sends a 6-digit verification code to the email. Unauthenticated; rate-limited. Then call account_signup_verify.
account_signup_verifyCreate a ZenSched org (step 2 of 2): verify the emailed code. Returns org_id and your zsc_ API key (shown once). Claude.ai must then Connect → Sign in with the same email — do not keep calling org tools until Connect succeeds.
account_recover_startLost API key (step 1 of 2): sends a verification code to the org owner email. Then call account_recover_verify. Prefer account_signin_start if you only need to reconnect — Recover revokes ALL keys.
account_recover_verifyLost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.
account_signin_startReconnect an existing org without rotating keys (step 1 of 2): emails a 6-digit code to the owner. Then account_signin_verify. Prefer this over Recover.
account_signin_verifyReconnect an existing org without rotating keys (step 2 of 2): verify the emailed code. Call this after account_signin_start. If later org tools fail, call account_signin_verify again or account_use_key.
account_use_keyAuthenticate this connector with an existing zsc_ API key. Prefer this when the key is already in the conversation. If the connector shows Connected but org tools fail, call this or account_signin_start — do not look for a Connect button.
account_auth_statusCheck whether this connector is signed in as a ZenSched org. Call this before account_get in a new session. Unauthenticated; never errors.