Manage Authentik through AI assistants
Authentik MCP server exists for a simple reason — assistants are far more useful when they can act on Authentik directly instead of describing what you should do. Manage Authentik through AI assistants.
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.
Once Authentik is connected, these are the calls the assistant has available:
authentik_admin_system_info — Get system information including HTTP host, runtime environment, server time, and embedded outpost statusauthentik_admin_version — Get Authentik version information including current version and build hashauthentik_admin_settings_get — Get current system settingsauthentik_admin_settings_update — Update system settings (partial update)authentik_admin_apps — List installed Django applications in the Authentik instanceauthentik_admin_models — List all data models available in the Authentik instanceauthentik_admin_version_history — List Authentik version history entriesauthentik_admin_system_task_trigger — Trigger all system tasks (e.g., cleanup, cache clear)authentik_authenticators_list — List all authenticator devices across all types for the current userauthentik_authenticators_admin_by_type_list — List authenticator devices of a specific type (admin view)authentik_authenticators_admin_by_type_get — Get a single authenticator device by type and ID (admin view)authentik_authenticators_admin_by_type_delete — Delete an authenticator device by type and ID (admin view)The server ships on npm as @samik081/mcp-authentik, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 2 environment variables: AUTHENTIK_URL, AUTHENTIK_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Authentik's toolset — authentik_admin_system_info, authentik_admin_version, authentik_admin_settings_get and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Samik081; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Authentik's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| authentik_admin_system_info | Get system information including HTTP host, runtime environment, server time, and embedded outpost status |
| authentik_admin_version | Get Authentik version information including current version and build hash |
| authentik_admin_settings_get | Get current system settings |
| authentik_admin_settings_update | Update system settings (partial update) |
| authentik_admin_apps | List installed Django applications in the Authentik instance |
| authentik_admin_models | List all data models available in the Authentik instance |
| authentik_admin_version_history | List Authentik version history entries |
| authentik_admin_system_task_trigger | Trigger all system tasks (e.g., cleanup, cache clear) |
| authentik_authenticators_list | List all authenticator devices across all types for the current user |
| authentik_authenticators_admin_by_type_list | List authenticator devices of a specific type (admin view) |
| authentik_authenticators_admin_by_type_get | Get a single authenticator device by type and ID (admin view) |
| authentik_authenticators_admin_by_type_delete | Delete an authenticator device by type and ID (admin view) |
| authentik_authenticators_user_by_type_list | List authenticator devices of a specific type for the current user |
| authentik_users_list | List users with optional filters for username, email, name, active status, superuser status, path, groups, and search |
**Docker (stdio):**
```json
{
"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"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTHENTIK_URL | Endpoint or connection string the server talks to. | Yes |
| AUTHENTIK_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.