Ext Ops Panel
Open dashboard
Comparison

Zoom vs Turniermeister — Tournament Engine

Zoom is a plugin bundle for AI coding tools published by Zoom. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Turniermeister — Tournament Engine is an MCP server published by MartyMcFlyJr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceZoomTurniermeister — Tournament Engine
Claude: knowledge-work-plugins Listed
Version: 1.1.0
Forks (GitHub): 3 583
Stars (GitHub): 32 412
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 Turniermeister — Tournament Engine
FactZoomTurniermeister — Tournament Engine
Marketplaces that list it11
Stars (GitHub) (differs)32 412 (better)0 (worse)
Forks (GitHub) (differs)3 583 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (app.turniermeister.at/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-pluginsgithub.com/martymcflyjr/turniermeister
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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.

Turniermeister — Tournament Engine

In its own words, on Official MCP Registry:

Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link.

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

Turniermeister — Tournament Engine As a remote MCP server

Claude Code
claude mcp add --transport http turniermeister https://app.turniermeister.at/mcp

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

Only Turniermeister — Tournament Engine 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: Turniermeister — Tournament Engine · 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