lmstudio-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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: opencode-bridge
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
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
Shared notes, logs, issues and secrets for Claude, ChatGPT and local models.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.518 npm26AGPL 3.0
- AlicenseAqualityDmaintenanceLets Claude Code delegate coding tasks to external models running on a local opencode serve, preserving main agent tokens for planning and review.866 npm1MIT
- AlicenseNot gradedqualityDmaintenanceBridges LM Studio local models to Claude Code as MCP tools, enabling private and free AI-assisted subtasks. Includes respond and models tools with automatic model selection and structured output.1MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate agent tasks to local LLMs via llama.cpp or vLLM servers on your own hardware, reducing API usage while maintaining full agent capabilities.1119MIT