Ext Ops Panel
Open dashboard
Comparison

Okta vs Microsoft 365 Calendar

Okta is an MCP server published by okta. Marketplaces we read that list it: 1 (Docker MCP Catalog). Microsoft 365 Calendar is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceOktaMicrosoft 365 Calendar
Docker MCP Catalog Listed
Version: sha256:f8330e18913b
Forks (GitHub): 61
Pulls (Docker Hub): 6 938
Stars (Docker Hub): 0
Stars (GitHub): 73
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 350
Downloads/week (npm): 28
Forks (GitHub): 4
Stars (GitHub): 13
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 Microsoft 365 Calendar
FactOktaMicrosoft 365 Calendar
Marketplaces that list it11
Stars (GitHub) (differs)73 (better)13 (worse)
Pulls (Docker Hub) (differs)6 938No figure on Docker Hub
Forks (GitHub) (differs)61 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/okta-mcp-server)On your machine (@mindstone/mcp-server-microsoft-calendar)
Transportstdiostdio
Tools it declares (differs)108Not published
Environment variables it asks for (differs)7, secrets among them: 15, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/okta/okta-mcp-servergithub.com/mindstone/mcp-servers
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:

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

Microsoft 365 Calendar

In its own words, on Official MCP Registry:

Microsoft 365 Outlook calendar via Graph: list, get, create, update, respond, free/busy.

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)

Microsoft 365 Calendar As a local MCP server: npm package

Claude Code
claude mcp add --env "MS_CLIENT_ID=<YOUR_MS_CLIENT_ID>" --env "MS_CONFIG_DIR=<YOUR_MS_CONFIG_DIR>" --transport stdio mcp-server-microsoft-calendar -- npx -y @mindstone/mcp-server-microsoft-calendar

Requires: MS_CLIENT_ID, MS_CONFIG_DIR

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

Tools each declares

The marketplaces of Microsoft 365 Calendar 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 Microsoft 365 Calendar asks for

  • MICROSOFT_REQUEST_TIMEOUT_MS
  • MS_ACCOUNT_EMAIL
  • MS_CLIENT_ID
  • MS_CONFIG_DIR
  • MS_MCP_PACKAGE_ID

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

What it can do: Okta · What it can do: Microsoft 365 Calendar · 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