Ext Ops Panel
Open dashboard
Comparison

lm-assist vs Orchestrator

lm-assist is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑30.

lm-assist is a plugin bundle for AI coding tools published by langmartai. No marketplace we read lists it any more. 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-08. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacelm-assistOrchestrator
Community marketplace langmartai/lm-assist Removed on 2026-10-30
Version: 0.2.5
Forks (GitHub): 4
Stars (GitHub): 17
Not marked · First seen
Not listed
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
PyPI (MCP servers) 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

lm-assist vs Orchestrator
Factlm-assistno longer listed · Orchestrator
Marketplaces that list it (differs)02
Stars (GitHub) (differs)1710
Forks (GitHub) (differs)42
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (orchestrator-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)7Not a bundle
Licence (differs)AGPL-3.0-or-laterMIT
Repository (differs)github.com/langmartai/lm-assistgithub.com/crak1644/orchestrator-mcp
Changes in the last 7 days00
First seen (differs)2026-10-262026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of lm-assist

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Claude Platform Docs

    Search and read the Claude Platform documentation and API reference.

    by platform.claude.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • madrox

    MCP server that orchestrates multiple Claude CLI instances as parallel workers with a real-time dashboard

    by barkain · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • memoriant-llm-gateway-skill

    Compliance-first LLM gateway for Claude Code. Policy-as-code enforcement (YAML policy definitions), tamper-evident audit trails, PII redaction, token budget enforcement, and…

    by NathanMaine · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • toolweave

    One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.

    by andreysparish · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • ai-adoption

    Two skills for analyzing your Claude history. token-doctor diagnoses where your Claude Code + Cowork spend goes, including sub-agent fan-out and model mix. task-profile mines…

    by Jeroen Van Hautte · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ccam-devtools

    Developer tools for Claude Code Agent Monitor — session debugging, hook diagnostics, data export, and system health checks for maintaining a healthy monitoring setup.

    by Son Nguyen · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

lm-assist

In its own words, on Community GitHub marketplaces:

Full observability & control for the Claude product line. 860+ API endpoints, 280+ MCP tools, 15 insight views, web terminal, fleet, missions, service connectors.

Orchestrator

In its own words, on Official MCP Registry:

Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.

How to run each

lm-assist

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 Code
claude mcp add --env "ORCHESTRATOR_CONFIG=<YOUR_ORCHESTRATOR_CONFIG>" --env "ORCHESTRATOR_HOST_RUNTIME=<YOUR_ORCHESTRATOR_HOST_RUNTIME>" --transport stdio orchestrator-mcp -- uvx orchestrator-mcp-server

Requires: 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 lm-assist publish no settings it asks for, so we do not compare settings.

What it can do: lm-assist · What it can do: Orchestrator · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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