mlx-serve/Comparison · LM Studio

The LM Studio alternative
that wins on the same file.

Identical weights, identical Mac, identical prompts, shipping defaults on both sides — mlx-serve decodes +26% faster (geomean) with +36% prefill on MLX models. Native menu-bar app, MIT license, no Electron, no Python.

Try it — keeps your models See the benchmarks
Finds your LM Studio models — no re-download MIT licensed ~4.5 MB server binary

Every cell, every model

Shipping defaults on both sides, same machine, same prompts, identical MLX weight files. Reproduce with tests/bench.sh --family all --lmstudio --omlx --mtplx — the harness ships in the repo.

+26%
decode geomean on identical MLX weights, shipping defaults
+145%
Qwen 3.6 27B, same file · the MTP head LM Studio leaves unused
+117%
Gemma 4 E4B prefill · identical weights
7.7×
faster warm time-to-first-token
Benchmark chart: mlx-serve vs LM Studio, oMLX and MTPLX on Gemma 4 and Qwen 3.6, code completion decode, shipping defaults
Six models, code completion decode, v26.8.3. LM Studio 0.4.19+2, oMLX 0.5.2 and MTPLX 2.5.3 beside mlx-serve, every engine on its shipping defaults, all loading the identical MLX weight files.

What you gain by switching

Capabilitymlx-serveLM Studio
MLX + GGUF models
Decode speed, identical weights (defaults)+26% geomeanbaseline
OpenAI-compatible API
Anthropic Messages API (Claude Code)partial
OpenAI Responses API + WebSocketspartial
Ollama API (drop-in for Ollama clients)
Speculative decoding (PLD + drafter + MTP)
KV-cache quantization
Continuous batching
Agent mode + MCP client 10 tools
Sandboxed agent shell (Linux VM)
DeepSeek V4 Flash (284B) via ds4
Image / video / voice generation, local
App runtimeNative SwiftElectron
LicenseMITProprietary

Feature set as of v26.8.7. Benchmark details, CSVs, and the reproduction harness live in the repo.

Migration

Switching takes one download — yours is the only one you skip

MLX Core reads LM Studio's own ~/.lmstudio/settings.json and auto-discovers your existing model folder, so everything you've already downloaded shows up in the picker immediately — MLX and GGUF alike. Your OpenAI-compatible clients keep working too: same wire protocol, just a different port.

  • Zero re-downloads — your LM Studio model folder is auto-discovered.
  • Same API shape — point Continue, Cursor, Open WebUI at the new port.
  • Plus Claude Code — fuller Anthropic-endpoint coverage than LM Studio’s newer compat layer.
  • Signed & notarized — no "unidentified developer" dialogs.

Switching questions, answered

Is mlx-serve really faster than LM Studio?

Yes. On the v26.8.3 matrix (M4 Max, LM Studio 0.4.19+2, identical MLX weight files, both engines on shipping defaults) mlx-serve decodes +26% geomean and prefills +36% geomean across the four models LM Studio also has. The separation is prefill (+117% on E4B) and speculative decoding: on Qwen 3.6 27B mlx-serve loads the checkpoint's MTP head and LM Studio does not, which is +145% on the same file. The benchmark harness ships in the repo so you can reproduce it on your own machine.

Do I have to re-download my models?

No. MLX Core auto-discovers LM Studio's model folder via ~/.lmstudio/settings.json — everything on disk appears in the picker. A custom-folder picker covers models stored anywhere else.

What does it add beyond speed?

Deeper Anthropic Messages (Claude Code works natively) and OpenAI Responses coverage than LM Studio’s newer compatibility endpoints — including a WebSocket transport and response compaction — a drop-in Ollama API, agent mode with MCP, an isolated Linux VM for agent shell commands, speculative decoding, KV-cache quantization, continuous batching, DeepSeek V4 Flash, and fully local image, video, and voice generation.

Is it open source?

Yes — MIT license, server and app both. LM Studio is proprietary freeware; mlx-serve you can read, fork, and ship.

More deep dives

Same models. Faster engine.

Download MLX Core — it finds your LM Studio models on first launch, so the switch costs you nothing but the download.