ShiftZap Restaurant Scheduling

io.github.samueldesignsaPublished by GitHub account samueldesignsav1.0.1Updated Oct 24, 2026

Manage restaurant employee scheduling, time-off, tips, and payroll via ShiftZap.

Overview

AI-generated overview

Local MCP server that connects an assistant to ShiftZap for restaurant employee scheduling, time-off, tips and payroll.

What you can do
  • Manage restaurant employee scheduling through ShiftZap.
  • Handle time-off requests.
  • Work with tips and payroll data.
  • No individual tools are documented in the supplied listing, so the exact actions available are not specified.
When to use it
Useful if your restaurant runs on ShiftZap and you want an assistant to help with staff scheduling, time-off, tips or payroll tasks from a desktop MCP client.
Requirements
Runs as a local process over stdio, installed from the npm package @shiftzap/mcp-server, so Node.js is needed. Requires a ShiftZap API key supplied in the SHIFTZAP_API_KEY environment variable. Desktop client only; no web executable.
Before you install
The server needs a ShiftZap API key (SHIFTZAP_API_KEY, a live key) that grants access to your restaurant's scheduling, time-off, tips and payroll data. Scheduling and payroll changes may affect employees and pay, so review any write actions before confirming. Tool-level permissions are not documented.

Installation

In SourceWeft

  1. Open ShiftZap Restaurant Scheduling in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.