ceos/unsloth
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
unsloth/studio/MCP.md
Michael Han 6d8c18cd1a
 Replace standalone Studio wording with Unsloth (#7221) 
* Replace standalone Studio wording with Unsloth

Replace the single word Studio with Unsloth wherever it is used as
shorthand for Unsloth Studio in docs, CLI output, UI strings, i18n
locales, workflow display names, comments and docstrings.

Kept unchanged: the full name Unsloth Studio, third party product
names (LM Studio, Visual Studio, Mac Studio), feature names
(Recipe Studio, Fine-tuning Studio and its translations), and all
identifiers such as env vars, commands, paths and filenames.

* Address review feedback on the Studio wording rename

Use "an" before Unsloth where the rename left the article as "a".
Restore the split brand where Unsloth and Studio render as two halves
of the full product name: the onboarding sidebar subtitle and the
IPv6 localhost warning. Scope two messages to the full name Unsloth
Studio where plain Unsloth was misleading: the AMD README bullet and
the CLI studio setup error.
2026-07-19 00:47:04 -07:00

1.4 KiB
Raw Permalink Blame History

Unsloth Studio MCP server

Unsloth can expose a local MCP server so an MCP client can inspect models and GPU state, validate recipes, start or stop training, inspect recipe output, and export a loaded model.

The server is disabled by default. Enable it for a local Unsloth process with:

UNSLOTH_STUDIO_ENABLE_MCP=1 \
UNSLOTH_STUDIO_MCP_TOKEN='use-a-local-secret' \
unsloth studio

The endpoint is http://127.0.0.1:8888/mcp/ when Unsloth uses its default port (a request to /mcp redirects to the canonical /mcp/). Use the actual Unsloth port when it is configured differently.

The high-impact tools are:

  • studio_status and list_local_models for discovery
  • get_training_status, start_training, stop_training, and list_training_runs
  • validate_recipe, get_recipe_job_status, and get_recipe_job_dataset
  • load_checkpoint and export_gguf

start_training accepts the same fields as the Unsloth TrainingStartRequest. The request is validated by the existing Pydantic model before a subprocess is started. Export paths use the existing Unsloth validation as well.

The endpoint always requires UNSLOTH_STUDIO_MCP_TOKEN and checks an exact Bearer token for both HTTP and WebSocket connections. Keep it on localhost unless the deployment has an authenticated reverse proxy. The MCP endpoint is intentionally opt-in because tools can consume GPU memory, write model artifacts, and stop active work.