mcp-server-lmstudio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| ask_local_llmC | Send a prompt or coding question to the local LLM running in LM Studio. |
| list_local_modelsA | List currently loaded and available models in LM Studio. |
| check_lm_studio_statusB | Check if LM Studio local server is currently running and accessible. |
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 3 tools
Each tool targets a clearly distinct function: listing models, asking the LLM, and checking server status. There is no overlap or ambiguity between them.
All names use snake_case with a consistent verb-first pattern (list_, ask_, check_). The minor variation in object wording reflects their distinct targets rather than inconsistent convention.
Three tools are well-scoped for the narrow purpose of interacting with a local LM Studio server. Each tool earns its place and no tool feels redundant or missing at this scale.
Core operations for checking status, listing models, and querying the LLM are covered. Minor gaps exist, such as model load/unload or generation parameter control, but these are not essential for basic use.