Okta Auth MCP 服务器 | PlugMCP
跳到正文 okta-auth
Alpha : this project is under active development. APIs, tool signatures, and
session formats may change between releases.
okta-auth is an Okta login toolkit with two entry points:
okta: interactive CLI for humans
okta-auth: MCP server for AI agents that reuse saved sessions
CLI and MCP server for Okta SSO authentication with persistent session management
把任意工具接入任意智能体。面向非开发者的 MCP 服务器目录;网关承载流量,n8n 承载应用。
产品
目录
开发者
公司
Sessions are stored under ~/.okta-auth/sessions/. Existing sessions under
~/.okta-auth-mcp/sessions/ are migrated automatically.
Install
uv tool uv tool install okta-auth-cli
pipx pipx install okta-auth-cli
pip pip install okta-auth-cli
Browser setup The project uses Playwright for browser automation. It automatically prefers a
local Chrome or Edge install when available.
If no supported system browser is found, install Playwright Chromium:
playwright install chromium
Upgrade
uv tool: uv tool upgrade okta-auth-cli
pipx: pipx upgrade okta-auth-cli
pip: pip install -U okta-auth-cli
Quick Start
1. Configure credentials If the wizard asks for a TOTP secret and you are not sure where to find it, see
TOTP Secret .
The wizard supports two providers:
keyring: store credentials in the OS credential manager
op: generate ~/.okta-auth/op.env with op://... references for op run
Only non-secret settings such as the default URL and provider metadata are stored
in ~/.okta-auth/config.json.
2. Log in Or pass a target URL directly:
okta https://portal.company.com
The login flow is headless by default. Use --headed to show the browser.
3. Reuse the session from MCP Once configured, AI agents can authenticate with the saved session or with the
credential provider you configured.
TOTP Secret The TOTP secret is the Base32 key behind your authenticator app. You typically
must capture it during initial MFA enrollment.
During Okta MFA setup
Go to Settings -> Security Methods in Okta.
Choose Google Authenticator or another TOTP-compatible factor.
On the QR screen, click Can't scan?
Copy the displayed Base32 secret.
Complete enrollment by entering the generated code.
This project does not currently support portals that rely only on the Okta Verify
push app for MFA.
If you already enrolled and lost the secret You usually need to remove and re-enroll the authenticator factor to get a new
secret.
Credential Setup Credential resolution order is:
Explicit CLI or MCP arguments
Environment variables
Stored keyring credentials when the selected provider is keyring
Recommended: OS keyring This is the default and recommended local setup:
okta config --provider keyring
username, password, totp_secret: OS keyring only
default_url: ~/.okta-auth/config.json
Typical keyring backends:
macOS: Keychain Access
Windows: Credential Manager / Credential Locker
Linux: Secret Service or KWallet
If no secure backend is available, the wizard refuses to fall back to plaintext.
1Password CLI If you already manage secrets in 1Password:
okta config --provider op
vault, item, field names, default_url: ~/.okta-auth/config.json
OKTA_USERNAME, OKTA_PASSWORD, optional OKTA_TOTP_SECRET references:
~/.okta-auth/op.env
The generated env file contains op://... references, not plaintext values.
Launch the CLI or MCP server through op run:
op run --env-file=$HOME/.okta-auth/op.env -- okta
op run --env-file=$HOME/.okta-auth/op.env -- uvx --from okta-auth-cli okta-auth
1Password vault, item, and field names must be compatible with secret reference
paths. If a name contains unsupported separators such as /, use the object's
unique ID instead.
Environment variables Environment variables are still supported for CI, ephemeral shells, or external
secret managers. They override okta config values.
export OKTA_USERNAME="[email protected] "
export OKTA_PASSWORD="your-okta-password"
export OKTA_TOTP_SECRET="JBSWY3DPEHPK3PXP"
Manual 1Password setup If you do not want to use the wizard, you can set up op run manually.
op item create --category login --title "Okta MCP" \
username="[email protected] " \
password="your-okta-password" \
totp_secret="JBSWY3DPEHPK3PXP"
Create ~/.okta-auth/op.env:
OKTA_USERNAME=op://Personal/Okta MCP/username
OKTA_PASSWORD=op://Personal/Okta MCP/password
OKTA_TOTP_SECRET=op://Personal/Okta MCP/totp_secret
op run --env-file=$HOME/.okta-auth/op.env -- uvx --from okta-auth-cli okta-auth
CLI
Common commands
okta [url]: log in and save a session
okta config: open the credential wizard
okta config --provider keyring: force keyring configuration
okta config --provider op: force 1Password configuration
okta config --show: show current config status
okta config --reset: remove saved config and credentials
okta check <url>: verify a stored session
okta list: list stored sessions
okta delete <url>: delete a stored session
okta cookies <url>: inspect stored cookies
Example
MCP Server
MCP tools
Claude Code claude mcp add okta-auth -- uvx --from okta-auth-cli okta-auth
claude mcp add okta-auth -- op run --env-file=$HOME/.okta-auth/op.env -- uvx --from okta-auth-cli okta-auth
Claude Desktop / Cursor / Windsurf {
"mcpServers": {
"okta-auth": {
"command": "uvx",
"args": ["--from", "okta-auth-cli", "okta-auth"]
}
}
}
{
"mcpServers": {
"okta-auth": {
"command": "op",
"args": ["run", "--env-file=/Users/yourname/.okta-auth/op.env", "--", "uvx", "--from", "okta-auth-cli", "okta-auth"]
}
}
}
Use okta for the interactive CLI. Use okta-auth only when wiring the package
into an MCP client.
Security
This project is intended for local trusted execution.
Session files and cookies are sensitive credentials.
Prefer okta config over passing credentials directly on the command line.
Prefer keyring or op run over plaintext shell files.
Never post cookie values, passwords, or TOTP secrets in issues or logs.
Development uv venv && source .venv/bin/activate
uv pip install -e '.[dev]'
playwright install chromium
ruff format --check .
ruff check .
pytest
Worldmonitor Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface Strix Open-source AI penetration testing tool to find and fix your app’s vulnerabilities. MCP For Beginners This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for Casdoor An open-source Agent-first Identity and Access Management (IAM) /LLM MCP & agent gateway and auth server with web UI supporting OpenClaw, MCP, OAuth, OIDC, SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA, Ida Pro AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP. NPM Sentinel MCP Provide AI-powered real-time analysis and intelligence on NPM packages, including security, dependencies, performance, and quality metrics. Enable faster and safer package management decisions by inte Ida Pro AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP. Hexstrike Ai HexStrike AI MCP Agents is an advanced MCP server that lets AI agents (Claude, GPT, Copilot, etc.) autonomously run 150+ cybersecurity tools for automated pentesting, vulnerability discovery, bug boun Nist Nvd Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE. GhidraMCP MCP Server for Ghidra GhidraMCP MCP Server for Ghidra ComplianceCheckup Free automated privacy grades (A+ to F) for 900+ SaaS tools, plus GDPR, HIPAA, PCI DSS, SOC 2, CCPA, and ADA compliance checklists with source citations. Security MCP 服务器 最佳 Security MCP 服务器 reverse-engineer-anything Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a c rea-ci-tests-audit Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testi
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
如何安装 Okta Auth? 在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 配置。它使用发布者的安装方式,而不是 PlugMCP 代理。
Okta Auth 需要 API 密钥吗? 此记录未列出必需的环境变量。
Okta Auth 使用哪种传输方式? Okta Auth 通过 stdio 在本地运行。
Okta Auth 上次检查是什么时候? 上次检查时间:2026-10-27。 CLI and MCP server for Okta SSO authentication with persistent session management
工具
0 / 10