Ext Ops Panel
Open dashboard
Comparison

Orchestrate vs MediaWiki MCP Server

Orchestrate is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). MediaWiki MCP Server is an MCP server published by ProfessionalWiki. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceOrchestrateMediaWiki MCP Server
Cursor: cursor/plugins Listed
Version: 1.1.0
Forks (GitHub): 1 086
Stars (GitHub): 11 186
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.19.0
Forks (GitHub): 41
Stars (GitHub): 136
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

Orchestrate vs MediaWiki MCP Server
FactOrchestrateMediaWiki MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)11 186 (better)136 (worse)
Forks (GitHub) (differs)1 086 (better)41 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published18, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/professionalwiki/mediawiki-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (11 h 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

Orchestrate

In its own words, on Cursor: cursor/plugins:

Fan large tasks out across parallel cloud agents with planners, workers, verifiers, and structured handoffs.

MediaWiki MCP Server

In its own words, on Official MCP Registry:

MCP server enabling AI clients to interact with any MediaWiki wiki through standard tools

How to run each

Orchestrate

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

MediaWiki MCP Server

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.

Only MediaWiki MCP Server 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

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

What it can do: Orchestrate · What it can do: MediaWiki MCP Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-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