First release of mcp-mayo — an MCP server that exposes MAYO Apollo HRM (Foundation / Attendance / Payroll) as AI-callable tools.
Highlights
- 33 tools — 28 thin per-endpoint wrappers + 5 semantic compositions
- Three backend domains served behind a single
hrmlicenseAPI key - Date-format normalization — callers use ISO
YYYY-MM-DD/YYYY-MM; internally converted to MAYO'sYYYY/MM/DD/YYYY/MMwhere needed - Multi-domain REST connector with retry and structured
MayoAPIError - Dual-language docs (English + 繁體中文)
- Connection test probing all three backends
- E2E runner with
KNOWN ISSUElabelling for upstream-broken endpoints
Verified (PRE environment)
- All three domains reachable with a valid
hrmlicensekey - 24 / 33 tools return real data end-to-end
- 9 tools labelled
KNOWN ISSUE— 4 already flagged by MAYO as upstream failures (trip_history + three monthly insurance endpoints) and 5 tied to/ClientOut/ReportCenter/*routes that currently 404 on the PRE Foundation backend
Installation
uv add mcp-mayo
# or
pip install mcp-mayoSet MAYO_API_KEY to your hrmlicense token and run uvx mcp-mayo (or wire it into Claude Desktop / Claude Code / Cursor — see the README for client configs).