LM Studio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LMSTUDIO_HOST | No | LM Studio host | 127.0.0.1 |
| LMSTUDIO_PORT | No | LM Studio port | 1234 |
| LMSTUDIO_BASE_URL | No | Full WebSocket URL for LM Studio (used if set, otherwise derived from HOST and PORT) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check connectivity to LM Studio server |
| list_modelsA | List all downloaded LLM models available in LM Studio |
| list_loaded_modelsA | List all currently loaded LLM models in LM Studio |
| load_modelB | Load a model into memory in LM Studio |
| unload_modelB | Unload a model from memory in LM Studio |
| get_model_infoA | Get detailed information about a specific loaded model in LM Studio |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: health_check for connectivity, list_models vs list_loaded_models for different sets, get_model_info for details on a loaded model, and load/unload for lifecycle management. No ambiguity.
Most tools follow a verb_noun pattern (get_model_info, list_choices, load_model, unload_model). health_check deviates as a noun phrase but is conventional and understandable. Overall consistent.
With 6 tools covering connectivity, listing, loading/unloading, and info query, the count is well-scoped for the domain of model management without bloat or deficiency.
The set covers core model lifecycle (load, unload, list, info) and connectivity. Minor gaps like model deletion or parameter configuration are not critical for common agent tasks.