Loading repository data…
Loading repository data…
fctr-id / repository
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
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
This release introduces powerful special tools that revolutionize daily Okta administration tasks:
💡 Real-World Example - Access Analysis:
❓ Question: "Can user john@company.com 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 dan@company.com'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