ZenSched — field workforce scheduling for agents

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

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://zensched--mikef.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "ZenSched — field workforce scheduling for agents": {
      "url": "https://zensched--mikef.run.tools"
    }
  }
}

能力清单

工具	说明
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 submission.
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.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。