Skip to main content
Glama
bunizao

okta-auth

by bunizao

okta_login

Idempotent

Authenticate to a website via Okta SSO, including TOTP MFA, and save the browser session for reuse.

Instructions

Authenticate to a website via Okta SSO and persist the session.

Launches a headless browser, navigates to the target URL, performs Okta login (including TOTP MFA if configured), and saves the browser session for later use. Sessions are stored per-domain in ~/.okta-auth/sessions/.

Credentials are resolved in order: explicit parameter → environment variable → OS keyring when the local provider is set to keyring. When the provider is set to op, launch the server through op run so the environment is populated at process start.

Args: url: Target URL to authenticate against (e.g., 'https://portal.company.com'). username: Okta username or email. Falls back to OKTA_USERNAME or stored keyring data. password: Okta password. Falls back to OKTA_PASSWORD or stored keyring data. totp_secret: Base32 TOTP secret for automated MFA. Falls back to OKTA_TOTP_SECRET or stored keyring data. headed: Show the browser window during login. Set to true for debugging. timeout_ms: Maximum time in ms to wait for page loads (5000-300000, default 60000).

Returns: JSON: {"success": bool, "domain_key": str|null, "message": str, "url": str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
headedNo
passwordNo
usernameNo
timeout_msNo
totp_secretNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (idempotent, non-destructive), the description reveals that the tool launches a headless browser, performs TOTP MFA if configured, persists sessions to ~/.okta-auth/sessions/, and details credential fallback logic. This provides substantial behavioral context that aids agent decision-making.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: opening purpose sentence, brief behavioral overview, standalone credential resolution paragraph, clearly labeled Args section, and Returns specification. Every sentence contributes value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, 1 required, credential fallback, MFA handling, session persistence), the description covers the overall flow, parameter details, return format, and credential resolution. The output schema is described in the Returns section, making it self-contained. Minor details like error handling could be inferred from the 'message' field in the return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by documenting all 6 parameters in an Args section. It explains fallback order for credentials (explicit → env var → keyring), the purpose of 'headed' for debugging, and timeout range/default. This adds critical meaning beyond the schema's bare names and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence clearly states the tool's function: 'Authenticate to a website via Okta SSO and persist the session.' This specific verb+resource combination immediately distinguishes it from sibling tools (check, list, delete, get_cookies) which deal with session inspection and cleanup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (to perform Okta login including MFA) and gives detailed information about credential resolution order and headed mode for debugging. However, it does not explicitly exclude alternatives or mention when not to use this tool, though the context of sibling tools makes this largely inferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bunizao/okta-auth'

If you have feedback or need assistance with the MCP directory API, please join our Discord server