LM Studio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LM_STUDIO_BASE_URL | No | Base URL for LM Studio API | http://localhost:1234 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List all available models in LM Studio with their current state (loaded/not-loaded) |
| get_model_detailsB | Get detailed information about a specific model including architecture, quantization, and context length |
| load_modelB | Load a model into memory with configurable Time-To-Live (TTL). The model will auto-unload after the TTL expires. |
| unload_modelB | Unload a model from memory immediately by setting its TTL to 0 |
| configure_modelC | Configure model settings such as TTL and draft model for speculative decoding |
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 5 tools
Tools have largely distinct purposes: list_models for overview, get_model_details for specifics, load/unload for state changes, configure_model for settings. However, load_model and configure_model both involve TTL, and unload_model is essentially a special case of configure_model (TTL=0), creating minor overlap.
All tool names follow a consistent snake_case verb_noun pattern: list_models, get_model_details, load_model, unload_model, configure_model. No deviations.
Five tools is well-scoped for model lifecycle management in LM Studio. Each tool covers a distinct operation without redundancy.
The surface covers listing, inspecting, loading, unloading, and configuring models, which is solid for model management. Minor gaps include no tool for downloading or deleting model files, but these may be outside the server's scope.