Is this an official Okta MCP server?

No. It is Memtro's MCP server with Memtro's Okta connector behind it: the connector reads Okta through its API with the credentials you connect on Dashboard → Connections, and Okta publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Okta?

Not yet. Today every Okta tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

Okta MCP server

Okta in any MCP client, through Memtro: Okta does not publish this server. Memtro's Okta connector reads Okta through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only identity directory from Okta: find people and their status, groups and memberships, applications and who has access to them, and the system log of sign-ins and admin events.

Reads

okta_search_usersFind people in Okta by name, email or login (prefix match), optionally by status (ACTIVE, SUSPENDED, DEPROVISIONED…) or department.
okta_get_userOne person by Okta id, login or email with their profile, status, groups and the applications assigned to them.
okta_groupsGroups with member and app counts, searched by name prefix; or one group (by id or exact name) with its members.
okta_appsApplications integrated with Okta: label, status (ACTIVE/INACTIVE), sign-on mode (SAML_2_0, OPENID_CONNECT, BROWSER_PLUGIN…), created/updated.
okta_app_usersWho has access to an application: the people assigned (directly or through a group), their status and the groups that grant access.
okta_system_logSystem log events (sign-ins, MFA, app access, admin changes) for a time window, newest first, with counts by event type and outcome.

Connect it

First connect Okta on Dashboard → Connections, then add Memtro to your client once. The Okta tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Okta connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who has access to Salesforce in Okta?
› Is jane.doe@acme.com still active, and when did she last sign in?
› Which groups is Sam in?
› List failed sign-ins in the last 24 hours
› Which apps are still using SWA instead of SAML?

Questions

Is this an official Okta MCP server?: No. It is Memtro's MCP server with Memtro's Okta connector behind it: the connector reads Okta through its API with the credentials you connect on Dashboard → Connections, and Okta publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Okta?: Not yet. Today every Okta tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.