Ext Ops Panel
Open dashboard
Comparison

Okta vs gws

Okta is an MCP server published by okta. Marketplaces we read that list it: 1 (Docker MCP Catalog). gws is a plugin bundle for AI coding tools published by orieg. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceOktagws
Docker MCP Catalog Listed
Version: sha256:f8330e18913b
Forks (GitHub): 60
Pulls (Docker Hub): 6 698
Stars (Docker Hub): 0
Stars (GitHub): 71
Not marked · First seen
Not listed
Community marketplace orieg/gws-connector Not listed Listed
Version: 0.4.3
No figure published
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 gws
FactOktagws
Marketplaces that list it11
Stars (GitHub) (differs)71No figure on GitHub
Pulls (Docker Hub) (differs)6 698No figure on Docker Hub
Forks (GitHub) (differs)60No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/okta-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)108Not published
Environment variables it asks for (differs)7, secrets among them: 11, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle9
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/okta/okta-mcp-servergithub.com/orieg/gws-connector
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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).

gws

In its own words, on Community GitHub marketplaces:

Multi-account workspace integration — Mail, Calendar, Drive, Sheets, and Docs with smart account routing for Gmail and Google Workspace

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)

gws As a Claude Code plugin

Claude Code
/plugin marketplace add orieg/gws-connector
/plugin install gws@gws-connector

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

Tools each declares

The marketplaces of gws 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 gws asks for

  • GWS_STATE_DIR

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

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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