Ext Ops Panel
Open dashboard
Comparison

Okta vs onecli

Okta is an MCP server published by fctr-id. Marketplaces we read that list it: 1 (Docker MCP Catalog). onecli is a plugin bundle for AI coding tools published by onecli. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceOktaonecli
Docker MCP Catalog Listed
Version: sha256:8d6cd51e1836
Forks (GitHub): 8
Pulls (Docker Hub): 33 337
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.4
Forks (GitHub): 1
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 onecli
FactOktaonecli
Marketplaces that list it11
Stars (GitHub) (differs)38 (better)1 (worse)
Pulls (Docker Hub) (differs)33 337No figure on Docker Hub
Forks (GitHub) (differs)8 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/okta-mcp-fctr)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)20Not published
Environment variables it asks for (differs)4, secrets among them: 1Not published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle7
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/fctr-id/okta-mcp-servergithub.com/onecli/onecli-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11

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:

Secure Okta identity and access management via Model Context Protocol (MCP). Access Okta users, groups, applications, logs, and policies through AI assistants with enterprise-grade security.

onecli

In its own words, on Claude Code: claude-plugins-community:

Connect AI agents to external APIs with zero credential management. The OneCLI gateway transparently proxies all HTTPS traffic and injects stored credentials (OAuth tokens, API keys, AWS signatures) into outbound requests. Supports 40+ services including GitHub, Gmail, Google Calendar, Jira, AWS, Stripe, Datadog, and more. Policy rules enforce block, rate limit, and manual approval at the gateway level.

How to run each

Okta As a local MCP server: Docker image

Claude Code
claude mcp add --env "OKTA_API_TOKEN=<YOUR_OKTA_API_TOKEN>" --transport stdio okta-mcp-fctr -- docker run -i --rm -e OKTA_API_TOKEN mcp/okta-mcp-fctr

Requires: OKTA_API_TOKEN (secret)

onecli

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

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

Settings each asks for

The marketplaces of onecli publish no settings it asks for, so we do not compare settings.

What it can do: Okta · What it can do: onecli · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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