com.zensched/zensched · v1.0.0 · communication
ZenSched is healthy: it completed an MCP handshake in 2207 ms and exposes 11 tools.
Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.
Endpoint: https://mcp.zensched.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 11 |
| Latency | 2207 ms |
| Last checked (UTC) | 2026-10-14T23:00:36.362Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T23:00:36.362Z | Healthy | 2207 |
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_submit). |
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, medium, high, blocker. Include related_tool and paste error text in context when reporting a bug. A human reads every |
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 account_set_contact. Rate-limited aggressively. |
account_signup_start | Create 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_verify | Create 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_start | Lost 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_verify | Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys. |
account_signin_start | Reconnect 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_verify | Reconnect 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_key | Authenticate 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_status | Check whether this connector is signed in as a ZenSched org. Call this before account_get in a new session. Unauthenticated; never errors. |