ZenSched
Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"zensched": {
"url": "https://mcp.zensched.com/mcp"
}
}
}Remote endpoints
https://mcp.zensched.com/mcpstreamable-httpWhat it can do
Tool inventory
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).
Input Schema
{
"type": "object",
"properties": {},
"title": "zensched_guideArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "zensched_guideOutput"
}🟡feedback_submit(title, body, category, severity, related_tool, ...)
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.
Input Schema
{
"type": "object",
"properties": {
"title": {
"title": "Title",
"type": "string"
},
"body": {
"title": "Body",
"type": "string"
},
"category": {
"default": "other",
"title": "Category",
"type": "string"
},
"severity": {
"default": "medium",
"title": "Severity",
"type": "string"
},
"related_tool": {
"default": "",
"title": "Related Tool",
"type": "string"
},
"context": {
"default": "",
"title": "Context",
"type": "string"
},
"idempotency_key": {
"default": "",
"title": "Idempotency Key",
"type": "string"
}
},
"required": [
"title",
"body"
],
"title": "feedback_submitArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "feedback_submitOutput"
}🟡account_create(org_name)
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.
Input Schema
{
"type": "object",
"properties": {
"org_name": {
"title": "Org Name",
"type": "string"
}
},
"required": [
"org_name"
],
"title": "account_createArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_createOutput"
}🟡account_signup_start(org_name, email)
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.
Input Schema
{
"type": "object",
"properties": {
"org_name": {
"title": "Org Name",
"type": "string"
},
"email": {
"title": "Email",
"type": "string"
}
},
"required": [
"org_name",
"email"
],
"title": "account_signup_startArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_signup_startOutput"
}🟡account_signup_verify(email, code)
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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
},
"code": {
"title": "Code",
"type": "string"
}
},
"required": [
"email",
"code"
],
"title": "account_signup_verifyArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_signup_verifyOutput"
}⚪account_recover_start(email)
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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
}
},
"required": [
"email"
],
"title": "account_recover_startArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_recover_startOutput"
}🔴account_recover_verify(email, code)
Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
},
"code": {
"title": "Code",
"type": "string"
}
},
"required": [
"email",
"code"
],
"title": "account_recover_verifyArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_recover_verifyOutput"
}⚪account_signin_start(email)
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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
}
},
"required": [
"email"
],
"title": "account_signin_startArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_signin_startOutput"
}⚪account_signin_verify(email, code)
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.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
},
"code": {
"title": "Code",
"type": "string"
}
},
"required": [
"email",
"code"
],
"title": "account_signin_verifyArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_signin_verifyOutput"
}⚪account_use_key(api_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.
Input Schema
{
"type": "object",
"properties": {
"api_key": {
"title": "Api Key",
"type": "string"
}
},
"required": [
"api_key"
],
"title": "account_use_keyArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_use_keyOutput"
}🟢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.
Input Schema
{
"type": "object",
"properties": {},
"title": "account_auth_statusArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "account_auth_statusOutput"
}Community
Evidence