Authentik MCP Server

MCP Authentik

MCP server for Authentik identity management. Manage users, groups, applications, flows, policies, providers, and more through natural language in Cursor, Claude Code, and Claude Desktop.

Features

• 297 tools across 22 categories covering the complete Authentik API
• Read-only mode via AUTHENTIK_ACCESS_TIER=read-only for safe monitoring
• Category filtering via AUTHENTIK_CATEGORIES to expose only the tools you need
• Type-safe SDK client via @goauthentik/api
• Docker images for linux/amd64 and linux/arm64 on GHCR
• Remote MCP via HTTP transport (MCP_TRANSPORT=http) using the Streamable HTTP protocol
• TypeScript/ESM with full type safety

API Compatibility

Built for Authentik 2026.5.

Quick Start

Run the server directly with npx:

AUTHENTIK_URL="https://auth.example.com" \

AUTHENTIK_TOKEN="your-api-token" \ npx -y @samik081/mcp-authentik

The server validates your Authentik connection on startup and fails immediately with a clear error if credentials are missing or invalid.

Docker

Run with Docker (stdio transport, same as npx):

docker run --rm -i \

-e AUTHENTIK_URL=https://auth.example.com \ -e AUTHENTIK_TOKEN=your-api-token \ ghcr.io/samik081/mcp-authentik

To run as a remote MCP server with HTTP transport:

docker run -d -p 3000:3000 \

-e MCP_TRANSPORT=http \ -e AUTHENTIK_URL=https://auth.example.com \ -e AUTHENTIK_TOKEN=your-api-token \ ghcr.io/samik081/mcp-authentik

The MCP endpoint is available at http://localhost:3000 and a health check at http://localhost:3000/health.

Configuration

Claude Code CLI (recommended):

# Using npx

claude mcp add --transport stdio authentik \ --env AUTHENTIK_URL=https://auth.example.com \ --env AUTHENTIK_TOKEN=your-api-token \ -- npx -y @samik081/mcp-authentik

Using Docker

claude mcp add --transport stdio authentik \ --env AUTHENTIK_URL=https://auth.example.com \ --env AUTHENTIK_TOKEN=your-api-token \ -- docker run --rm -i ghcr.io/samik081/mcp-authentik

Using remote HTTP (connect to a running Docker container or HTTP server)

claude mcp add --transport http authentik http://localhost:3000

JSON config (works with Claude Code .mcp.json, Claude Desktop claude_desktop_config.json, Cursor .cursor/mcp.json):

{

"mcpServers": { "authentik": { "command": "npx", "args": ["-y", "@samik081/mcp-authentik"], "env": { "AUTHENTIK_URL": "https://auth.example.com", "AUTHENTIK_TOKEN": "your-api-token" } } } }

Docker (stdio):

{

"mcpServers": { "authentik": { "command": "docker", "args": ["run", "--rm", "-i", "-e", "AUTHENTIK_URL=https://auth.example.com", "-e", "AUTHENTIK_TOKEN=your-api-token", "ghcr.io/samik081/mcp-authentik" ] } } }

Remote MCP (connect to a running Docker container or HTTP server):

{

"mcpServers": { "authentik": { "type": "streamable-http", "url": "http://localhost:3000" } } }

Access Tiers

Control which tools are available using the AUTHENTIK_ACCESS_TIER environment variable:

• full: All 297 tools. Includes creating, updating, and deleting users, groups, applications, flows, providers, and all other resources.
• read-only: 144 tools. Listing and viewing resources only. No state changes.

Tools that are not available in your tier are not registered with the MCP server. They will not appear in your AI tool's tool list, keeping the context clean.

Environment Variables

Available Categories

admin, authenticators, core, crypto, endpoints, enterprise, events, flows, managed, oauth2, outposts, policies, property-mappings, providers, rac, rbac, reports, root, sources, ssf, stages, tenants

Tools

mcp-authentik provides 297 tools organized by category. Each tool's Access column shows the minimum tier required: read-only (available in both tiers) or full (requires full tier). The Hints column shows tool behavior: read-only (no state changes), destructive (modifies existing state), idempotent (same result if called twice).

Admin (8 tools)

Authenticators (5 tools)

Core (45 tools)

Users

Groups

Applications

| `authentik_apps_updat