Senzii Scheduling MCP server
com.senzii/scheduling·v1.0.1·2 starsOpen-source staff scheduling: skills matching, shifts, certifications. Self-hostable, MCP-native.
2 stars
Reviews
Write oneNobody has reviewed Senzii Scheduling yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Senzii Scheduling tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 25 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
How Senzii Scheduling compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Release history: 2 versions in the registry since 2026-08-02, latest 2026-09-28, typically one every 57 days.
Install Senzii Scheduling in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Senzii Scheduling repository's README, as published. We do not edit it. Read it on GitHub
Senzii Scheduling App & MCP Server
Staff scheduling your AI agent can operate directly. Senzii is an open-source (Apache-2.0) scheduling platform: tag-based skills matching, shift assignment with conflict detection, certification tracking, proximity ranking, and client staffing requests — exposed as MCP tools for Claude, ChatGPT, or any MCP-compatible client.
The MCP server ships inside this repo and shares the app's PostgreSQL schema — it is the scheduling engine's agent interface, not a generic database connector.
MCP tools
28 tools covering the full scheduling workflow:
Every tool is scoped to the authenticated organization — the org ID is injected server-side into every query, so cross-org data access is impossible. Assignments are created pending by design: the agent proposes, a human confirms before the schedule goes live. That is a deliberate safety choice for regulated industries, not a limitation.
Stack
- Web framework: FastAPI
- Database: asyncpg (PostgreSQL)
- Sessions: Cookie-based, PostgreSQL-backed
- Email: Resend API (optional — only for notification features; the app runs fine without a key)
- Geocoding: Nominatim (OpenStreetMap) — free public endpoint, no API key
- MCP Server: Python MCP SDK (Streamable HTTP)
Requirements
Quick Start
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env # set DATABASE_URL and SESSION_SECRET (generate: python -c "import secrets; print(secrets.token_urlsafe(48))"); add RESEND_API_KEY only for email features
uvicorn app.main:app --host 0.0.0.0 --port 3000 --reloadMCP server:
python -m mcp_server.mainTool definitions live in mcpserver/tools/tools.toml — add or modify tools by editing the TOML and their handlers under mcpserver/tools/.
Architecture
app/
main.py — FastAPI app, all routers wired
config.py — Environment configuration
db/ — Database layer (asyncpg pool, migrations, queries)
models/ — Pydantic schemas
middleware/ — Auth session extraction, rate limiting
routes/ — FastAPI routers (1:1 with Rust routes)
services/ — Email (Resend), Geocoding (Nominatim)
mcp_server/ — MCP server (Python MCP SDK), tools defined in tools.toml
static/ — App HTML/CSS/JS (login, dashboards, portals, SEO pages)The marketing/landing site is a separate repo (Senzii-App/site) served from Vercel at senzii.com. app.senzii.com serves only the app: GET / is the sign-in page.
Deployment
Two targets, one CLI (see infra/README.md for full docs):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-11-01restoreF → Cscore 65
Senzii Scheduling: common questions
- Is Senzii Scheduling MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Senzii Scheduling safety report
- Does Senzii Scheduling need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Senzii Scheduling maintained?
- The last commit was 29 days ago (2026-10-06). The latest release is v1.0.1.
- How does Senzii Scheduling compare with other MCP servers?
- safety score 65/100 (higher than 20% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.