Ext Ops Panel
Open dashboard
Comparison

Orchestrate vs io.github.jyswee/taufunctions

Orchestrate is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.jyswee/taufunctions is an MCP server published by jyswee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceOrchestrateio.github.jyswee/taufunctions
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: 1.2.5
Downloads/month (npm): 796
Downloads/week (npm): 60
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

Orchestrate vs io.github.jyswee/taufunctions
FactOrchestrateio.github.jyswee/taufunctions
Marketplaces that list it11
Stars (GitHub) (differs)11 186 (better)0 (worse)
Forks (GitHub) (differs)1 086 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.taufunctions.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/jyswee/taufunctions
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

io.github.jyswee/taufunctions

In its own words, on Official MCP Registry:

Serverless functions for coding agents. Deploy, invoke, monitor. 13 tools, stdio or remote.

How to run each

Orchestrate

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

io.github.jyswee/taufunctions As a remote MCP server

Claude Code
claude mcp add --transport http taufunctions https://mcp.taufunctions.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: TAU_API_KEY (secret), Authorization header

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

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: io.github.jyswee/taufunctions · 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