lmstudio-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lmstudio-mcpsummarize the last 200 lines of this build log"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
lmstudio-mcp
An MCP server that lets Claude Code delegate easy, mechanical tasks (summaries, boilerplate, reformatting, test data) to local models running in LM Studio — keeping Claude as the orchestrator while cheap work runs locally.
Tools
Tool | Purpose |
| Send a self-contained prompt to a local model. Optional |
| List models currently available in LM Studio. |
The ask_local_model tool description tells Claude when to delegate (mechanical, low-stakes tasks with small context) so delegation happens automatically once the server is installed.
Related MCP server: LibreModel MCP Server
Requirements
Node.js 18+
LM Studio running with its local server enabled (default
http://localhost:1234) and at least one chat model loaded
Setup
git clone https://github.com/zmagyar/lmstudio-mcp.git
cd lmstudio-mcp
npm install
# register with Claude Code (user scope = available in all projects)
claude mcp add --scope user lmstudio -- node "$(pwd)/index.js"Start a new Claude Code session and try: "use the local model to summarize this file".
Configuration
Set via environment variables (e.g. in the server's entry in ~/.claude.json):
Variable | Default | Purpose |
|
| LM Studio API endpoint |
|
| Model used when Claude doesn't specify one |
Set LMSTUDIO_DEFAULT_MODEL to a model you actually have loaded — run lms ls or check the LM Studio UI.
Making delegation automatic
Out of the box, Claude only uses the tools when you ask ("use the local model to…"). Two extra steps make it delegate small tasks on its own, without prompting you each time — sample files for both are in examples/:
Standing instructions — append the contents of
examples/CLAUDE.md.sampleto your~/.claude/CLAUDE.md(create it if missing). It's loaded into every session and tells Claude when to delegate: mechanical, low-stakes tasks like log summaries, boilerplate, and reformatting — and when not to.Pre-approved permissions — merge the
permissionsblock fromexamples/settings.json.sampleinto your~/.claude/settings.json, so the tool calls don't stop at a permission prompt. If you already have apermissions.allowarray, just add the two entries to it.
Both changes take effect in your next Claude Code session. Try "summarize the last 200 lines of this build log" — the lmstudio tool should fire without being asked for.
Note that delegation is judgement-based: Claude decides per-task using those instructions, so tune the wording in your CLAUDE.md if it delegates too eagerly or too rarely.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zmagyar/lmstudio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server