Back to Home

MCP Documentation

ZenSched

Connect your AI assistant to manage vendor field operations through plain English.

Which Product?

ZenSched is for vendor field operations (assigning workers to stores, managing check-ins). If you run roadshow product demos and staffing agencies, you want ZenShows instead.

ZenSched
MCP: https://mcp.zensched.com/mcp
Keys: Start with zsc_
Use case: Vendor field ops
ZenShows
MCP: https://www.zenshows.com/mcp
Keys: Start with zs_
Use case: Roadshow product demos

Connecting Your Assistant

ZenSched works with Claude Desktop, Cursor, and any MCP-compatible AI tool.

MCP server URL:

https://mcp.zensched.com/mcp

Getting your API key:

  1. If you are a new vendor, the assistant will walk you through OAuth account creation when you connect. No manual signup needed.
  2. If you already have a ZenSched account, generate an API key from your account settings. Keys start with zsc_. Paste that key when your MCP client asks for credentials.

Once connected, the assistant has read and write access to your locations, events, workers, forms, and check-ins. It cannot see data from other vendors.

Getting Started Workflow

A typical first-time setup looks like this:

  1. Create your organization (new vendors only). The assistant will prompt you through OAuth signup or key entry.
  2. Add a location. Tell the assistant the store name and address. Example: "Create a location for Target on Main Street in Columbus, Ohio."
  3. Create an event. Events are shifts at a store. Example: "Create a weekend demo event at that Target location, Saturday and Sunday 10 AM to 6 PM."
  4. Assign a form to the event. Forms capture what happened during the shift. Call form_assign with the form ID and event ID. Example: "Assign form 47 to that event."
  5. Invite a worker. Workers receive an invite link to accept the shift. Example: "Invite Maria Lopez, phone 555-1234, email maria@example.com, to that event."
  6. Fund the event if needed. Some accounts require funding before workers can check in. The assistant will tell you if funding is required.

After setup, workers check in through the mobile app or web portal. The assistant can retrieve check-in records, event summaries, and worker history on request.

Remote Check-In

By default, workers must be on-site (within the geofence) to check in. For remote work or distributed teams, disable geofencing when creating the event:

  • Set geofence_enabled=false
  • Set require_on_site=false

Tell the assistant: "Create a remote event" or "Allow remote check-in for this event."

What You Can Do

Once connected, ask the assistant to:

  • Create and update locations (stores, venues)
  • Schedule events (shifts) at those locations
  • Assign forms to events to capture field data
  • Invite workers and manage rosters
  • Retrieve check-in and check-out records
  • Pull event summaries and worker performance data
  • Adjust event settings (geofence, remote check-in, funding)

The assistant uses the same permissions as your user account. If your account cannot edit events or invite workers in the web UI, the assistant cannot do that either.

Questions or Issues?

If you run into trouble connecting, or if the assistant cannot complete an action you expect to work, reach out through your ZenSched account or email support@zensched.com.