Sytadel MCP Server
The Sytadel MCP Server exposes Sytadel identity and access operations as 5 typed tools for MCP clients like Claude Desktop and Cursor.
List tenant users with role, active flag, passkey count, and last login.
List service accounts across client apps with idle days and rotation state.
Query recent session anomalies for the calling user (IP/country/device/score), up to limit 200.
Compile natural-language RBAC intent into Sytadel PolicySet JSON (read-only, not applied).
Trigger an AI-driven access review returning a markdown report and machine-readable recommendations.
Authenticate via user mode (full admin scope) or service account mode (read-only tools only; admin tools return 403).
Tenant is always derived from the authenticated principal, never from a model-supplied argument.
Click on "Deploy 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., "@Sytadel MCP Server show me all service accounts with idle days"
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.
@sytadel/mcp-server
Model Context Protocol server that exposes Sytadel identity + access primitives as tools consumable from Claude Desktop, Cursor, and any MCP-aware client.
What it is
On its own: a standalone MCP server you point at any running Sytadel control plane (auth-api + zerotrust-api). It turns identity/access operations into typed tools an LLM client can call — the tenant is always derived from the authenticated principal, never from a model-supplied argument.
As part of Sytadel: it is the agentic surface of the suite. It talks to auth-api (identity) through zerotrust-api (policy gateway), so every tool call is subject to the same per-tenant authorization as any other client. It is a client of the plane — it needs auth-api reachable to do anything. See the suite architecture.
Ships 5 tools out of the box:
Tool | Description |
| Memberships of the current tenant with role, active flag, passkey count, last login |
| Client apps + their service accounts with idle days and rotation state |
| Recent flagged logins (IP / country / device / score) |
| Compile natural-language RBAC intent → Sytadel PolicySet JSON |
| Trigger the AI-driven access review and return the full report |
Related MCP server: Purple AI MCP Server
Installation
git clone https://github.com/ElwinErnst/sytadel-mcp-server
cd sytadel-mcp-server
npm install
npm run buildConfiguration
Auth has two modes — pick one depending on which tools you need:
User mode (recommended for operators)
Full role scope. Every admin-level tool (list_tenant_users, list_service_accounts, run_access_review) works.
export SYTADEL_TENANT_SLUG=your-tenant
export SYTADEL_USER_EMAIL=you@example.com
export SYTADEL_USER_PASSWORD=your-passwordService account mode
Restricted API_CLIENT scope. Read-only tools work (query_session_anomalies, generate_policy); admin tools return 403.
export SYTADEL_TENANT_SLUG=your-tenant
export SYTADEL_CLIENT_APP_ID=<uuid>
export SYTADEL_SERVICE_ACCOUNT_ID=<uuid>
export SYTADEL_SERVICE_ACCOUNT_SECRET=syt_...Endpoint URLs (optional overrides)
export SYTADEL_AUTH_API_URL=http://localhost:3002/api # default
export SYTADEL_ZT_API_URL=http://localhost:3010 # default
export SYTADEL_TIMEOUT_MS=60000 # default 60sWiring into Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"sytadel": {
"command": "node",
"args": ["/absolute/path/to/mcp-server/dist/index.js"],
"env": {
"SYTADEL_AUTH_API_URL": "http://localhost:3002/api",
"SYTADEL_ZT_API_URL": "http://localhost:3010",
"SYTADEL_TENANT_SLUG": "your-tenant",
"SYTADEL_USER_EMAIL": "you@example.com",
"SYTADEL_USER_PASSWORD": "your-password"
}
}
}
}Restart Claude Desktop. The 5 tools appear in the tool picker.
Wiring into Cursor
Same shape, different path: ~/.cursor/mcp.json (or via Settings → MCP → Add).
Local sanity check
With the Sytadel stack running (docker compose up -d at the repo root):
npm run build
SYTADEL_TENANT_SLUG=sentinel-labs \
SYTADEL_USER_EMAIL=admin@test.com \
SYTADEL_USER_PASSWORD=123456 \
node dist/index.jsThe server logs starting stdio server: ... connected — awaiting MCP client and waits for JSON-RPC on stdin.
Design notes
No third-party HTTP library. Everything uses native
fetch+AbortController.Token cache with 60s early refresh and inflight-request coalescing so parallel tool calls share one auth handshake.
Logs to stderr only. stdout is reserved for JSON-RPC framing; any
console.logon stdout corrupts the protocol.
License
PolyForm Strict 1.0.0 (source-available, noncommercial use only). See LICENSE.
Available Tools
5 toolsgenerate_policyA
Compile a natural-language RBAC intent (e.g. "OWNER can do anything, MEMBER can only GET /vaults, default deny") into a Sytadel PolicySet JSON. Returns policy, warnings, cost, tokens, latency. Read-only: the compiled policy is NOT applied — call PUT /policies/:tenantId separately to enforce it.
Inputs: intent (required).
list_service_accountsA
List service accounts (machine credentials) under every client app of the current tenant, with last-used timestamps and auto-rotation state. Useful for spotting dormant integrations.
Inputs: no named parameters.
list_tenant_usersA
List all users of the current Sytadel tenant with their role, active flag, passkey count, and last login. Useful for access reviews and off-boarding checks.
Inputs: no named parameters.
query_session_anomaliesA
Return recent session anomaly events (login from new IP / new country / new device / high score) for the calling user, up to limit rows. Ordered newest first.
Inputs: limit.
run_access_reviewA
Trigger an on-demand AI-driven access review for the current tenant. Claude reviews users, service accounts and recent anomalies, and returns a markdown report plus a machine-readable list of recommendations (revoke, downgrade, disable_service_account, rotate_service_account_secret, delete_passkey, require_password_reset, review_manually).
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: session anomalies, policy compilation, access reviews, user listing, and service account listing. There is no overlap or ambiguity between these functions.
All tool names use snake_case and a verb-object structure, but the verbs vary (list, query, generate, run). Two tools share the list prefix, but the inconsistent verbs prevent a perfect score.
Five tools is well-scoped for a server focused on access review and policy generation. Each tool addresses a key workflow without unnecessary bloat.
The set covers data retrieval (users, service accounts, anomalies) and generates policies/reviews. However, there is no tool to apply policies or act on review recommendations, creating a notable gap in the full lifecycle.
Maintenance
Related MCP Connectors
One MCP endpoint for your company's tools, with per-person sign-in, policy and audit.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceEnables interaction with Omada Identity Governance and Administration system for identity management, access requests, and compliance monitoring via MCP.1-
- AlicenseNot gradedqualityCmaintenanceEnables interaction with SentinelOne's security platform, including Purple AI, events, alerts, vulnerabilities, and asset inventory, through MCP.MIT
- AlicenseAqualityCmaintenanceEnables policy-first defensive security operations for MCP, providing repository and web-security analysis with controlled authorization, scoped execution, and auditability.91MIT
- AlicenseAqualityBmaintenanceEnables management of Scaleway IAM (applications, API keys, policies, permission sets) and Object Storage bucket policies through an MCP server.11720 npmMIT