NestDaddy

ZenSched

com.zensched/zensched · v1.0.0

Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.

Connect Remote server

Terminal
claude mcp add --transport http zensched https://mcp.zensched.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "zensched": {
      "url": "https://mcp.zensched.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "zensched": {
      "type": "http",
      "url": "https://mcp.zensched.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.zensched.com/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 11 found in our last check

  • 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.…

  • 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.

Headers

NameDescription
Authorization
Required, secret
API key as Bearer zsc_... Get a key at https://www.zensched.com/pricing/

Details

Endpointhttps://mcp.zensched.com/mcp (Streamable HTTP)
First published1 Sep 2026
Last updated1 Sep 2026
Registry namecom.zensched/zensched

More data and analytics servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.