lmstudio-local
Related Servers
Alternatives to lmstudio-local
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceEnables MCP clients to interact with local LLMs via LM Studio, supporting dynamic chat, vision, RAG, file interaction, and model orchestration.28-
- FlicenseAqualityCmaintenanceMCP server that connects LLM agents to a local LM Studio instance, enabling model management, OpenAI-compatible chat completions, text completions, and embeddings through a set of tools.91-
- AlicenseAqualityCmaintenanceEnables MCP clients to scan local GGUF models, estimate VRAM and suggest GPU offload layers, manage llama-server lifecycle, and proxy OpenAI-format chats with idle auto-unload.9MIT
- AlicenseNot gradedqualityCmaintenanceExposes local LM Studio language models as MCP tools, enabling chat completions and model listing through a local OpenAI-compatible API without requiring API keys.MIT

Local AI MCPofficial
AlicenseAqualityAmaintenanceUnified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.1618 npmCreative Commons Attribution Non Commercial No Derivatives 4.0 International- AlicenseAqualityDmaintenanceEnables listing, loading, unloading, and configuring models in LM Studio via MCP tools, with support for TTL and draft model settings.56MIT
TDQS
Scored across 28 tools
Many tools are distinct, but several clusters overlap: lm_load/lm_load_advanced/lm_model_config/lm_profiles all configure loading; lm_status/lm_diagnose/lm_runtime overlap in inspection/update; lm_chat/lm_openai_chat and lm_rag_ask/lm_rag_search differ mainly by interface. Descriptions clarify intent but misselection risk remains.
All 28 tools use the lm_ prefix and snake_case, with mostly predictable noun or verb_phrase patterns. lm_load_advanced is the only compound variation but remains readable and consistent with the set.
28 tools is heavy for a single MCP server and exceeds the 16-25 borderline range. While the broad LM Studio domain justifies many operations, the set could be consolidated, especially around load/config/profile tools.
The set covers runtime, models, loading, downloads, chats, RAG, MCP, docs, diagnostics, and server control, which is broad for the domain. Minor gaps like deleting models or more direct MCP server lifecycle management exist, but core local lifecycle coverage is mostly complete.