Orchestrate vs XFMS — Model Source
Orchestrate is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). XFMS — Model Source is an MCP server published by xpansion.dev. 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
| Marketplace |  XFMS — Model Source | |
|---|---|---|
| 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.4.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
| Fact | Orchestrate | XFMS — Model Source |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 186 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 086 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (xfms.vercel.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/visionairyse/xfms |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (25 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
Fan large tasks out across parallel cloud agents with planners, workers, verifiers, and structured handoffs.
XFMS — Model Source
Pick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators.
How to run each
Orchestrate
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
XFMS — Model Source As a remote MCP server
claude mcp add --transport http xfms https://xfms.vercel.app/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XFMS — Model Source 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: Orchestrate · What it can do: XFMS — Model Source · 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.