Ext Ops Panel
Open dashboard
Comparison

Okta vs MyOTP.App

Okta is an MCP server published by okta. Marketplaces we read that list it: 1 (Docker MCP Catalog). MyOTP.App is an MCP server published by brntech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOktaMyOTP.App
Docker MCP Catalog Listed
Version: sha256:f8330e18913b
Forks (GitHub): 61
Pulls (Docker Hub): 6 808
Stars (Docker Hub): 0
Stars (GitHub): 71
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.14
Downloads/month (npm): 444
Downloads/week (npm): 48
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Okta vs MyOTP.App
FactOktaMyOTP.App
Marketplaces that list it11
Stars (GitHub) (differs)71 (better)1 (worse)
Pulls (Docker Hub) (differs)6 808No figure on Docker Hub
Forks (GitHub) (differs)61 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/okta-mcp-server)Remote server (mcp.myotp.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)108Not published
Environment variables it asks for (differs)7, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/okta/okta-mcp-servergithub.com/brntech/myotp-agentkit
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (31 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Okta

In its own words, on Docker MCP Catalog:

## :tada: __It's Official__ :tada: The Okta Open-Source MCP Server integrates with LLMs and AI agents, allowing you to perform various Okta management operations using natural language and is Generally Available (GA).

MyOTP.App

In its own words, on Official MCP Registry:

Send and verify one-time passcodes over SMS, WhatsApp and Telegram.

How to run each

Okta As a local MCP server: Docker image

Claude Code
claude mcp add --env "OKTA_PRIVATE_KEY=<YOUR_OKTA_PRIVATE_KEY>" --transport stdio okta-mcp-server -- docker run -i --rm -e OKTA_PRIVATE_KEY mcp/okta-mcp-server

Requires: OKTA_PRIVATE_KEY (secret)

MyOTP.App As a remote MCP server

Claude Code
claude mcp add --transport http myotp https://mcp.myotp.app/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: MYOTP_API_KEY (secret), X-API-Key header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only MyOTP.App has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of MyOTP.App publish no list of tools, so we do not compare tools.

Settings each asks for

Only Okta asks for

  • OKTA_CLIENT_ID
  • OKTA_KEY_ID
  • OKTA_LOG_FILE
  • OKTA_LOG_LEVEL
  • OKTA_ORG_URL
  • OKTA_PRIVATE_KEY (secret)
  • OKTA_SCOPES

Only MyOTP.App asks for

  • MYOTP_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Okta · What it can do: MyOTP.App · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built