trw-mcp vs Orchestrator
trw-mcp is an MCP server published by wallter. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Orchestrator is an MCP server published by crAK1644. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-07. 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 |  trw-mcp |  Orchestrator |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 9.5.1 Downloads/month (PyPI): 4 740 Downloads/week (PyPI): 1 046 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.12.0 Downloads/month (PyPI): 6 410 Downloads/week (PyPI): 52 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.12.0 Downloads/month (PyPI): 6 410 Downloads/week (PyPI): 52 Forks (GitHub): 2 Stars (GitHub): 10 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 | trw-mcp | Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 10 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (trw-mcp) | On your machine (orchestrator-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | BUSL-1.1 | MIT |
| Repository (differs) | github.com/wallter/trw-mcp | github.com/crak1644/orchestrator-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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
trw-mcp
Engineering memory MCP server for Claude Code — patterns, gotchas, and project knowledge that persist across sessions
Orchestrator
Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.
How to run each
trw-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Orchestrator As a local MCP server: PyPI package
claude mcp add --env "ORCHESTRATOR_CONFIG=<YOUR_ORCHESTRATOR_CONFIG>" --env "ORCHESTRATOR_HOST_RUNTIME=<YOUR_ORCHESTRATOR_HOST_RUNTIME>" --transport stdio orchestrator-mcp -- uvx orchestrator-mcp-serverRequires: ORCHESTRATOR_CONFIG, ORCHESTRATOR_HOST_RUNTIME
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 trw-mcp publish no settings it asks for, so we do not compare settings.
What it can do: trw-mcp · What it can do: Orchestrator · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.