Ext Ops Panel
Open dashboard
Comparison

Zoom vs ADITUS Developer Portal MCP

Zoom is a plugin bundle for AI coding tools published by Zoom. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). ADITUS Developer Portal MCP is an MCP server published by developers.aditus.com. 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
MarketplaceZoomADITUS Developer Portal MCP
Claude: knowledge-work-plugins Listed
Version: 1.1.0
Forks (GitHub): 3 378
Stars (GitHub): 29 875
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Zoom vs ADITUS Developer Portal MCP
FactZoomADITUS Developer Portal MCP
Marketplaces that list it11
Stars (GitHub) (differs)29 875No figure on GitHub
Forks (GitHub) (differs)3 378No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (developers.aditus.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)33Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

Zoom

In its own words, on Claude: knowledge-work-plugins:

Plan, build, and debug Zoom integrations across REST APIs, Meeting SDK, Video SDK, webhooks, bots, and MCP workflows. Search meetings, retrieve recordings, access transcripts, and design AI-powered Zoom experiences.

ADITUS Developer Portal MCP

In its own words, on Official MCP Registry:

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

How to run each

Zoom As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install zoom-plugin@knowledge-work-plugins

ADITUS Developer Portal MCP As a remote MCP server

Claude Code
claude mcp add --transport http developer-portal https://developers.aditus.com/api/mcp

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

Only ADITUS Developer Portal MCP has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Zoom · What it can do: ADITUS Developer Portal MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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