Skip to content
ZenShows LLC logo

ZenShows LLC MCP server

Which MCP servers are ZenShows LLC's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to ZenShows LLC

Whose server it is
  • Registry namecom.zensched/zenschedverified in the MCP registry

The registry name sits under zensched.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools11
  • Server calls itselfZenSched
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 265 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • account_create change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 9 of 11 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer241 ms
  • Space in an agent's context≈ 1,192 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsB · 86 of 100
  • Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 9 of 11

What an agent can do with it

  • not sure · schedule shifts for field workers from an MCP client
  • not sure · collect GPS-verified check-ins and form responses
  • not sure · export verified timesheets for payroll runs

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: account_create

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-10-26
  • 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…

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "zensched": {
      "type": "http",
      "url": "https://mcp.zensched.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http zensched https://mcp.zensched.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.zensched.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.