Ext Ops Panel
Open dashboard
Comparison

dashAI (unofficial) vs Model Manager

dashAI (unofficial) is an MCP server published by Maarmapa. Marketplaces we read that list it: 1 (Official MCP Registry). Model Manager is an MCP server published by setheerwagen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplacedashAI (unofficial)Model Manager
Official MCP Registry Listed
Version: 0.3.1
Downloads/month (PyPI): 100
Downloads/week (PyPI): 36
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.6
Downloads/month (PyPI): 227
Downloads/week (PyPI): 158
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

dashAI (unofficial) vs Model Manager
FactdashAI (unofficial)Model Manager
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (dashai-mcp)On your machine (mcp-modelmanager)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 06, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/maarmapa/dashai-mcpgithub.com/setheerwagen/local-ai-mcp-servers
Changes in the last 7 days (differs)01
First seen2026-10-112026-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

dashAI (unofficial)

In its own words, on Official MCP Registry:

Train, track and query models on a running dashAI instance. Read-oriented, no delete tools.

Model Manager

In its own words, on Official MCP Registry:

Manage your local model machine over MCP: state, model pull/remove, service switch, LoRA training

How to run each

dashAI (unofficial) As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio dashai-mcp -- uvx dashai-mcp

Model Manager As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MM_CONTAINER_ROOT=<YOUR_MM_CONTAINER_ROOT>" --env "MM_VM_HOST=<YOUR_MM_VM_HOST>" --env "MM_VM_USER=<YOUR_MM_VM_USER>" --transport stdio mcp-modelmanager -- uvx mcp-modelmanager

Requires: MM_CONTAINER_ROOT, MM_VM_HOST, MM_VM_USER

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

Only dashAI (unofficial) asks for

  • DASHAI_ALLOW_REMOTE
  • DASHAI_BASE_URL
  • DASHAI_TIMEOUT

Only Model Manager asks for

  • MM_CONTAINER_ROOT
  • MM_ENABLED_OPERATIONS
  • MM_MAX_TIER
  • MM_VM2_HOST
  • MM_VM_HOST
  • MM_VM_USER

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: dashAI (unofficial) · What it can do: Model Manager · Compare two other plugins

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