Okta Mcp Server

Created By
fctr-ida year ago
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
Overview

what is okta-mcp-server?

The okta-mcp-server is an implementation of the MCP (Management Control Protocol) for Okta APIs, designed to facilitate secure and efficient management of user identities and access control.

how to use okta-mcp-server?

To use the okta-mcp-server, clone the repository from GitHub, configure the necessary environment variables, and run the server to interact with Okta APIs using the MCP protocol.

key features of okta-mcp-server?

  • Implementation of the MCP protocol for seamless integration with Okta APIs.
  • Secure management of user identities and access control.
  • Easy configuration and setup for developers.

use cases of okta-mcp-server?

  1. Integrating user management systems with Okta for enhanced security.
  2. Automating access control processes in enterprise applications.
  3. Developing custom applications that require secure identity management.

FAQ from okta-mcp-server?

  • What is the MCP protocol?

The MCP protocol is a standard for managing user identities and access control in a secure manner.

  • Is okta-mcp-server free to use?

Yes! The okta-mcp-server is open-source and available for free on GitHub.

  • How can I contribute to the project?

You can contribute by submitting issues, feature requests, or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fctr-id
Star
6
Language
Python
License
View license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago