Overview
What is Okta MCP Server?
A Model Context Protocol server that enables Claude to interact with Okta's user management system, providing comprehensive user and group management capabilities along with onboarding automation.
How to use Okta MCP Server?
Install dependencies with npm install, then configure Claude Desktop by adding the server to claude_desktop_config.json with the command node, a path to dist/index.js, and environment variables OKTA_ORG_URL and OKTA_API_TOKEN. After restarting Claude Desktop, you can ask Claude to manage Okta users and groups using natural language.
Key features of Okta MCP Server
- Retrieve detailed user information and status
- Search users by profile attributes with advanced operators
- Create, activate, suspend, unsuspend, and delete users
- Manage groups: create, list, delete, assign members
- Import users from CSV and automate onboarding workflows
- PII masking and error handling with fallback search logic
Use cases of Okta MCP Server
- Query user details, status, and last login from Okta
- Search for users by department, title, email, or other attributes
- Manage group membership: add or remove users from groups
- Onboard new hires by importing CSV data and provisioning applications
- Run complete onboarding workflows with group assignment and app provisioning
FAQ from Okta MCP Server
What are the prerequisites for running Okta MCP Server?
You need Node.js v16 or higher, the Claude Desktop App, an Okta Developer Account, and an Admin API Token from Okta.
How do I configure and start the server?
Install dependencies, build the project, then add the server to your Claude Desktop configuration with the command node, an absolute path to dist/index.js, and environment variables OKTA_ORG_URL (e.g., https://dev-123456.okta.com) and OKTA_API_TOKEN. Restart Claude Desktop to activate.
What search operators are supported for finding users?
Supported operators include eq (exact match), sw (starts with), ew (ends with), co (contains), and pr (present). Not all attributes support all operators; the server automatically falls back to client-side filtering when needed.
Is the onboarding automation feature production-ready?
The onboarding automation tools are experimental and may be subject to changes or limitations based on Okta’s API constraints. Use with caution in production environments.
How are credentials and data handled?
The server uses the Okta API token and org URL provided as environment variables. API tokens should be kept secure, never committed to version control, and rotated regularly. PII masking is enabled for sensitive search parameters.
