ZenSched

com.zenschedPublished by zensched.comOfficial publisherv1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

ZenSched is a remote MCP server for field workforce scheduling, letting an assistant manage orgs, locations, workers, shifts, GPS punches and timesheets.

What you can do
  • Create and sign in to a ZenSched organization, including email-code signup, key-based sign-in, key recovery and auth status checks
  • Authenticate the connector with an existing API key and check whether it is signed in
  • Follow the built-in agent guide covering connect, funding, locations, workers, shifts and timesheets
  • Submit feedback, bug reports and feature requests, even without an account
When to use it
Use it when an assistant should set up and operate field workforce scheduling for an organization: creating the account, adding locations and workers, scheduling shifts and handling timesheets and GPS punches, without a separate dashboard.
Requirements
Remote streamable HTTP endpoint; no local package. Requires a bearer API key in the Authorization header, obtained from the provider's pricing page or issued by the account creation tools. Signup, sign-in and recovery flows send a 6-digit code to an owner email address.
Before you install
The API key is a secret and is shown only once; store it securely. Recovery issues a new key and revokes all previous keys, so prefer sign-in when reconnecting. Account creation is rate-limited, and the guide mentions funding, which may involve payment. The server can create and change organization, worker, shift and timesheet data.

Installation

In SourceWeft

  1. Open ZenSched in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.zensched%2Fzensched/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zensched": {
      "type": "http",
      "url": "https://mcp.zensched.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

11

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

Takes no parameters.

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.

Parametersbodyrequiredtitlerequiredcontextcategoryseverityrelated_toolidempotency_key

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.

Parametersorg_namerequired

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.

Parametersemailrequiredorg_namerequired

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.

Parameterscoderequiredemailrequired

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.

Parametersemailrequired

account_recover_verify

Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.

Parameterscoderequiredemailrequired

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.

Parametersemailrequired

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.

Parameterscoderequiredemailrequired

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.

Parametersapi_keyrequired

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.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.