🎉 What's New in v0.1.1-BETA - Enterprise-Grade Special Tools!
This release introduces powerful special tools that revolutionize daily Okta administration tasks:
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
This release introduces powerful special tools that revolutionize daily Okta administration tasks:
The Okta MCP Server is a groundbreaking tool built by the team at Fctr that enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). Built specifically for IAM engineers, security teams, and Okta administrators, it implements the MCP specification to help work with Okta enitities
💡 Real-World Example - Access Analysis:
❓ Question: "Can user [email protected] access the application Salesforce?"
🤖 AI Response (30 seconds): "User John Smith can access Salesforce because:
1) User is ACTIVE ✅
2) User is assigned via group 'Sales Team' ✅,
3) Policy allows access with 2FA from corporate network or requires PUSH factor from external locations - user has PUSH enrolled ✅"
⏱️ Manual Process: Navigate Users → Find John → Check Status → Check App
Assignments → Check Group Memberships → Check Salesforce Assignments →
Review Access Policies → Check MFA Factors → Correlate Network Rules (10-15 min)
💡 Real-World Example - Login Risk Assessment:
❓ Question: "Is [email protected]'s recent login activity suspicious?"
🤖 AI Response (30 seconds): "LOW RISK - Dan exhibits excellent login
security patterns: consistent geographic area, same residential ISP,
stable device fingerprints, normal browser patterns, zero VPN/proxy
usage, all Okta risk scores LOW ✅"
⏱️ Manual Process: System Logs → Filter User → Check Locations → Review
IP Addresses → Cross-reference Network Zones → Analyze Device Patterns →
Check Geographic Impossibility → Review Behavioral Flags (15+ min)
tool_registry.py dependency for simpler, more maintainable codebasejwks_uri validation📝 Note: CLI clients and AI sampling features have been moved to
_Archived/folder due to pydantic-ai dependency conflicts (security vulnerability ). See_Archived/README.mdfor details.
Please read this section carefully before using Okta MCP Server.
When you make a request, the interaction happens directly between the LLM and the Okta MCP tools - the client application is no longer in the middle. All data returned by these tools (including complete user profiles, group memberships, etc.) is sent to and stored in the LLM's context during the entire transaction for that conversation.
Key Privacy Considerations:
MCP is designed for lightweight workflows similar to Zapier, not bulk data operations.
Recommendation: Limit requests to fewer than 100 entities per transaction. Avoid operations that require fetching large datasets or multiple API calls.
Examples:
❌ Avoid these types of requests:
✅ Better approaches:
💡 For larger data sets and complex queries: Consider using the Okta AI Agent for larger queries and data sets, The agent is being enhanced with similar "actionable" features to handle larger datasets and more complex scenarios in the very near future.
The HTTP transport modes (both Streamable HTTP and SSE) have significant security risks:
mcp-remoteBest Practice: Only use the STDIO transport method (default mode) unless you have specific security controls in place and understand the risks.
The Okta MCP Server currently provides the following tools:
Access Analysis & Troubleshooting
analyze_user_app_access - Complete user application access evaluation with policy analysis (replaces 10-15 minutes of manual Okta Admin Console navigation)Security & Risk Assessment
analyze_login_risk - Comprehensive login behavior analysis with VPN/Tor detection and geographic impossibility checks (answers "Is this user compromised?" instantly)⚡ Why These Matter: The two most common questions Okta admins face daily are "Why can't user X access application Y?" and "Is this login activity suspicious?". These special tools instantly provide comprehensive answers that would otherwise require extensive manual investigation across multiple Okta admin screens, policy reviews, and log analysis - transforming 15+ minute investigations into 30-second AI-powered insights.
User Management
list_okta_users - Retrieve users with filtering, search, and pagination optionsget_okta_user - Get detailed information about a specific user by ID or loginlist_okta_user_groups - List all groups that a specific user belongs tolist_okta_user_applications - List all application links (assigned applications) for a specific userlist_okta_user_factors - List all authentication factors enrolled for a specific userGroup Operations
list_okta_groups - Retrieve groups with filtering, search, and pagination optionsget_okta_group - Get detailed information about a specific grouplist_okta_group_members - List all members of a specific grouplist_okta_assigned_applications_for_group - List all applications assigned to a specific groupApplication Management
list_okta_applications - Retrieve applications with filtering, search, and pagination optionslist_okta_application_users - List all users assigned to a specific applicationlist_okta_application_group_assignments - List all groups assigned to a specific applicationPolicy & Network Management
list_okta_policy_rules - List all rules for a specific policy with detailed conditions and actionsget_okta_policy_rule - Get detailed information about a specific policy rulelist_okta_network_zones - List all network zones with IP ranges and configuration detailsSystem Log Events
get_okta_event_logs - Retrieve Okta system log events with time-based filtering and search optionsDate & Time Utilities
get_current_time - Get current UTC time in ISO 8601 formatparse_relative_time - Convert natural language time expressions to ISO 8601 formatAdditional tools for applications, factors, policies, and more advanced operations are on the roadmap and will be added in future releases.
✅ Python 3.8+ installed on your machine
✅ Okta tenant with appropriate API access
✅ An MCP-compatible AI client (Claude Desktop, Microsoft Copilot Studio, etc.)
⚠️ Important Model Compatibility Note:
Not all AI models work with this MCP server. Testing has only been performed with:
- GPT-4.0
- Claude 3.7 Sonnet
- Google-2.5-pro
You must use latest model versions that explicitly support tool calling/function calling capabilities. Older models or models without tool calling support will not be able to interact with the Okta MCP Server.
The Okta MCP Server supports multiple AI providers through its flexible configuration system. This allows you to connect to various large language models based on your specific needs and existing access.
# Clone the repository
git clone https://github.com/fctr-id/okta-mcp-server.git
cd okta-mcp-server
# Create and activate a virtual environment
python -m venv venv
source venv/bin/activate # On Windows use: venv\Scripts\activate
# Install dependencies
pip install -r requirements.txt
⚠️ NOTICE: If you clone this repository anew or pull updates, always make sure to re-run
pip install -r requirements.txtto ensure all dependencies are up-to-date.
Create a config file with your Okta settings:
📝 Note: Standalone CLI clients have been archived. For MCP host integration (Claude Desktop, VS Code, etc.), use the server directly with the JSON configuration below.
The Okta MCP Server supports multiple transport protocols:
claude_desktop_config.json:
{
"mcpServers": {
"okta-mcp-server": {
"command": "DIR/okta-mcp-server/venv/Scripts/python",
"args": [
"DIR/okta-mcp-server/main.py"
],
"env": {
"OKTA_CLIENT_ORGURL": "https://dev-1606.okta.com",
"OKTA_API_TOKEN": "OKTA_API_TOKEN"
}
}
}
}
Replace DIR with your absolute directory path and OKTA_API_TOKEN with your actual tokenCurrent Standard - Modern HTTP-based transport with advanced features:
Starting the Streamable HTTP Server:
# Start server with explicit risk acknowledgment
python main.py --http --iunderstandtherisks
# Server will start on http://localhost:3000/mcp
# Connect using streamable HTTP compatible clients
Features:
⚠️ EXTREMELY DANGEROUS - READ CAREFULLY
For MCP clients that don't natively support remote connections, you can use mcp-remote via NPX:
Prerequisites:
Setup:
# 1. Install mcp-remote globally
npm install -g @anthropic/mcp-remote
# 2. Start your Okta MCP Server in HTTP mode
python main.py --http --iunderstandtherisks
# 3. Configure your MCP client (e.g., Claude Desktop)
Claude Desktop Configuration:
{
"mcpServers": {
"okta-mcp-server": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:3000/mcp"
],
"env": {
"OKTA_CLIENT_ORGURL": "https://dev-1606.okta.com",
"OKTA_API_TOKEN": "your_actual_api_token"
}
}
}
}
🚨 CRITICAL SECURITY WARNINGS:
When might you need this approach:
⚠️ DEPRECATED: SSE transport is deprecated and not recommended for new implementations.
# Run in SSE mode (requires explicit risk acknowledgment)
python main.py --sse --iunderstandtherisks
The Okta MCP Server provides Docker images for all transport types, offering containerized deployment options.
STDIO Transport (Recommended): For Claude Desktop or other MCP clients, configure to use the Docker container:
{
"mcpServers": {
"okta-mcp-server": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "OKTA_CLIENT_ORGURL",
"-e", "OKTA_API_TOKEN",
"fctrid/okta-mcp-server:stdio"
],
"env": {
"OKTA_CLIENT_ORGURL": "https://your-org.okta.com",
"OKTA_API_TOKEN": "your_api_token"
}
}
}
}
Streamable HTTP Transport (Current Standard):
# Start the HTTP container
docker run -d --name okta-mcp-http \
-p 3000:3000 \
-e OKTA_API_TOKEN=your_api_token \
-e OKTA_CLIENT_ORGURL=https://your-org.okta.com \
fctrid/okta-mcp-server:http
# Configure your MCP client to connect to http://localhost:3000/mcp
SSE Transport (Deprecated - Not Recommended):
# Start the SSE container (deprecated)
docker run -d --name okta-mcp-sse \
-p 3000:3000 \
-e OKTA_API_TOKEN=your_api_token \
-e OKTA_CLIENT_ORGURL=https://your-org.okta.com \
fctrid/okta-mcp-server:sse
# Configure your MCP client to connect to http://localhost:3000/sse
Building Images Locally:
# Build all variants
docker build --target stdio -t okta-mcp-server:stdio .
docker build --target http -t okta-mcp-server:http .
docker build --target sse -t okta-mcp-server:sse .
v0.1.0-BETA - Current (MAJOR ARCHITECTURAL OVERHAUL!)
v0.3.0 - Previous
Future plans include:
Before raising an issue, check:
Still having problems? Open an issue on GitHub or email [email protected] (response times may vary)
Have an idea or suggestion? Open a feature request on GitHub!
Interested in contributing? We'd love to have you! Contact [email protected] for collaboration opportunities.
Check out License.md for the fine print.
🌟 © 2025 Fctr Identity. All rights reserved. Made with ❤️ for the Okta and AI communities.
The Okta MCP Server is a groundbreaking tool built by the team at Fctr that enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). Built specifically
ภาพรวม
The Okta MCP Server is a groundbreaking tool built by the team at Fctr that enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). Built specifically for IAM engineers, security teams, and Okta administrators, it implements the MCP specification to help work with Okta enitities
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Okta ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-27 The Okta MCP Server is a groundbreaking tool built by the team at Fctr that enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). Built specifically for IAM engineers, security teams, and Okta administrators, it implements the MCP specification to help work with Okta enitities