ZenSched
Server Details
Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 11 tools
The account flows are mostly distinguishable: create, signup, signin, recover, and use_key have distinct purposes, and the descriptions include helpful preference guidance. The start/verify pairs and the similar signup/signin names create minor ambiguity, but descriptions resolve it.
Most tools follow a snake_case account_<action> pattern with clear start/verify pairs, and feedback_submit fits the verb_noun style. The naming is slightly inconsistent because zensched_guide is a bare noun and account_auth_status is not structured like the other action-oriented tools.
Eleven tools is within a reasonable range, and the multiple account tools each correspond to a distinct authentication flow. The count is slightly heavy on account management relative to the apparent scheduling domain, but no tool feels redundant.
The guide explicitly mentions fund, locations, workers, shifts, and timesheets, but none of those scheduling operations are exposed as tools. The server is essentially an account-authentication and feedback surface, and it even references missing tools like account_get and account_set_contact, so it severely under-serves the stated ZenSched purpose.
Available Tools
11 toolsaccount_auth_statusARead-onlyInspect
Check whether this connector is signed in as a ZenSched org. Call this before account_get in a new session. Unauthenticated; never errors.
Inputs: no named parameters. Returns: result
account_createAInspect
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.
Inputs: org_name (required). Returns: result
account_recover_startAInspect
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.
Inputs: email (required). Returns: result
account_recover_verifyADestructiveInspect
Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.
Inputs: code (required), email (required). Returns: result
account_signin_startAInspect
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.
Inputs: email (required). Returns: result
account_signin_verifyAInspect
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.
Inputs: code (required), email (required). Returns: result
account_signup_startAInspect
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.
Inputs: email (required), org_name (required). Returns: result
account_signup_verifyAInspect
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.
Inputs: code (required), email (required). Returns: result
account_use_keyAInspect
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.
Inputs: api_key (required). Returns: result
feedback_submitAInspect
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.
Inputs: body (required), title (required), context, category, +3 more. Returns: result
zensched_guideARead-onlyInspect
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).
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Headless field service software. Your AI agent runs jobs, schedules, quotes, invoices and payments.
Field operations on a deterministic solver — run jobs, crews & fleet from Claude or ChatGPT.
Run a service business from your AI agent: CRM, leads, scheduling, invoicing, jobs and more.
Hire AI workers that run on schedule, report back and act with your OK. Or deploy private models.
Related MCP Servers
- AlicenseBqualityBmaintenance67 tools generated from the same OpenAPI spec as our SDKs — CI fails on drift, so REST and MCP never disagree. Underneath: a deterministic field operations scheduling engine — skills, territories, live availability, sub-3-second cascade rescheduling — drivable end-to-end from Claude or ChatGPT. Schedule changes preview before they commit; LLMs never inside the math.5370 npm3MIT
- -licenseNot gradedqualityNot gradedmaintenanceField operations agent API for task management, geo-tracking, and team coordination. Built for African logistics, delivery, and field service teams.-
- AlicenseAqualityBmaintenanceEnables AI agents to schedule, reschedule, and cancel appointments for service businesses while enforcing availability, customer-confirmation, privacy, and staff-approval rules, with a tamper-evident audit log.6MIT
- AlicenseAqualityBmaintenanceLets AI agents work inside your own signed-in RazorSync account, so you can schedule and reassign jobs, create work orders, turn completed work into invoices, and follow up on unpaid bills using plain language. Works with Claude Code, ChatGPT, Cursor, and any MCP-capable agent, with a local stdio server that forwards tool calls to the hosted endpoint.7Elastic 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.