ComplyOS
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ComplyOSrun a compliance audit for the Engineering department"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ComplyOS
L&D Compliance & Learning Operations MCP Server
An AI-native compliance auditing engine for enterprise learning management systems. Built by someone who spent 12 years in L&D ops and got tired of explaining to regulators why the CSV export didn't match the dashboard.
Why ComplyOS?
Enterprise compliance tracking is a disaster of CSV exports, stale dashboards, and "I thought they completed that" moments. ComplyOS treats compliance as a first-class engineering problem:
Evidence-backed audits — Every report includes a SHA256-hashed evidence ledger
Assignment rule validation — Test targeting rules before they hit 10,000 users
AI-native interface — Query status via Claude Code, Cursor, or any MCP client
Local-first — SQLite by default; no SaaS lock-in
Related MCP server: RegGuard MCP Server
Architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ MCP Client │────▶│ ComplyOS MCP │────▶│ Compliance │
│ (Claude/Cursor) │ │ Server (FastMCP)│ │ Auditor │
└─────────────────┘ └──────────────────┘ └────────┬────────┘
│
┌──────────────────────────────┼──────────────┐
│ │ │
┌──────▼──────┐ ┌──────────▼─────┐ ┌────▼─────┐
│ Mock │ │ Workday │ │ SAP/CSOD│
│ Connector │ │ Connector │ │ (planned)│
└─────────────┘ └────────────────┘ └──────────┘Quick Start
Installation
# Clone the repo
git clone https://github.com/simongonzalezdc/complyos.git
cd complyos
# Install with uv (recommended)
uv sync --all-extras --dev
# Or with pip
pip install -e ".[dev]"CLI Usage
# Run a compliance audit
complyos audit
# Filter by department
complyos audit --department Engineering
# Generate a structured report
complyos report --department Engineering --json
# Check a single user's status
complyos status u1
# Sync LMS data to local SQLite
complyos sync
# Validate an assignment rule before deploying
complyos validate-rule rule.json
# Preview who would be affected by a rule
complyos preview-rule rule.json
# Check connector health
complyos healthMCP Server
# Start the MCP server
complyos mcpThen configure your MCP client (Claude Code, Cursor, etc.) to point to the server.
Connectors
Platform | Status | Auth |
Workday Learning | ✅ Supported | Basic Auth (env vars) |
Mock (seed data) | ✅ Built-in | None |
SAP SuccessFactors | 🚧 Planned | OAuth 2.0 |
Cornerstone OnDemand | 🚧 Planned | API Key |
Workday Configuration
Set environment variables:
export WORKDAY_BASE_URL="https://your-workday-instance.com"
export WORKDAY_USERNAME="your-user"
export WORKDAY_PASSWORD="your-pass"Development
# Run tests
uv run pytest -q
# Run with coverage
uv run pytest --cov=complyos --cov-report=term-missing
# Lint
uv run ruff check complyos tests
# Type check
uv run mypy complyos --ignore-missing-importsDomain Model
ComplianceGap(
user=User(id="u1", department="Engineering", ...),
missing_courses=[Course(code="SEC-101", mandatory=True)],
severity=ComplianceGapSeverity.HIGH, # critical | high | medium | low
days_overdue=14,
remediation_action=RemediationAction(...),
)Every audit produces an EvidenceLedgerEntry with SHA256 hashes for regulator-ready audit trails.
Roadmap
Phase 1 — Core auditor, MCP server, CLI, Workday connector, tests
Phase 2 — SQLite persistence, assignment rules engine, sync command
Phase 3 — Remediation workflows, Web UI, Slack/Teams notifications
License
Apache-2.0
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/simongonzalezdc/complyos'
If you have feedback or need assistance with the MCP directory API, please join our Discord server