MCP server for Authentik API integration with full capabilities
Listed on its own since 2026-09-24. Until then it was part of cdmx-authentik-mcp, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-cdmx-in-authentik-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Authentik MCP Server A Model Context Protocol (MCP) server that provides comprehensive integration with Authentik's API for user management, authentication flows, and system administration. ## Features ### User Management - Create, read, update, and delete users - Manage user groups and permissions - User search and filtering capabilities ### Group Management - Create and manage user groups - Assign users to groups - Group hierarchy management ### Application Management - Manage Authentik applications - Configure application providers - Application deployment and configuration ### Authentication Flows - View and manage authentication flows - Flow configuration and customization - Flow monitoring and diagnostics ### Event Monitoring - System event tracking and audit logs - Real-time event monitoring - Event filtering and search capabilities ### System Administration - API token management - Provider configuration - System health monitoring - Configuration management ## MCP Integration This server is designed to be used with MCP-compatible tools and platforms. It provides a standardized interface for interacting with Authentik instances through the Model Context Protocol. ### Configuration The server requires the following configuration parameters: - `base-url`: Base URL of your Authentik instance (required) - `token`: Authentik API token (required) - `verify-ssl`: Enable/disable SSL certificate verification (optional, default: true) ### Environment Variables You can also configure the server using environment variables: - `AUTHENTIK_BASE_URL`: Base URL of your Authentik instance - `AUTHENTIK_TOKEN`: Authentik API token - `AUTHENTIK_VERIFY_SSL`: SSL certificate verification (true/false) ## API Token Setup 1. Log in to your Authentik instance as an administrator 2. Navigate to **Directory** > **Tokens** 3. Click **Create** to create a new token 4. Choose the appropriate permissions for your use case 5. Copy the generated token for use with this MCP …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.