ZenSched
com.zensched/zenschedVersion 1.0.0Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.
Status
Responds335 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:23 UTC
- Latency
- 335 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.zensched.com/mcpResponds335 msNo sign-in
Claude Code
claude mcp add --transport http zensched https://mcp.zensched.com/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: zensched
Remote MCP server URL: https://mcp.zensched.com/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"zensched": {
"url": "https://mcp.zensched.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"zensched","type":"http","url":"https://mcp.zensched.com/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
11 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
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. | No | Yes | Not declared | No |
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. | No | No | Not declared | No |
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. | No | No | Not declared | Yes |
account_recover_verifyLost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys. | Yes | No | Not declared | No |
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. | No | No | Not declared | Yes |
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. | No | No | Not declared | No |
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. | No | No | Not declared | Yes |
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. | No | No | Not declared | No |
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. | No | No | Not declared | No |
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. | No | No | Not declared | Yes |
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). | No | Yes | Not declared | No |
Details
- Registry status
- Active
- Published
- Sep 1, 2026
- Updated
- Sep 1, 2026
- Repository
- Not given
- Categories (suggested)
- Time trackingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared