lmstudio-mcp
Related Servers
Alternatives to lmstudio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables locally configured MCP servers to be called over stdio and mixed with xAI server-side tools, without relying on hosted xAI MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to inspect Godot project and editor state, observe opted-in running scenes, manage processes, and apply permission-scoped guarded edits. It starts read-only and exposes additional capabilities only through explicit command-line flags.Apache 2.0
- AlicenseCqualityFmaintenanceThis MCP server gives an AI coding host controlled, client-agnostic access to a local machine's developer capabilities: transactional file edits, shell and PTY execution, Git and project inspection, language-server operations, isolated browser automation, Windows UI automation, VS Code state, durable jobs, and checkpoints, all bounded by filesystem root allowlisting and resource admission controls. It speaks standard MCP over stdio, Streamable HTTP, and legacy HTTP+SSE, and can also run headless as a long-lived job runner without any hosted model vendor.114ISC

Msty Local Opsofficial
AlicenseAqualityAmaintenanceA fail-closed MCP server for Msty Studio on macOS that provides read-only diagnostics and an optional bounded local-generation tool, without accessing chats, keys, or configuration.4MIT- AlicenseAqualityBmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.8MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to control a local computer over stdio with filesystem operations, ripgrep search, shell command execution, and persistent process sessions.14MIT
TDQS
Scored across 18 tools
Each tool has a clearly distinct purpose: status, diagnostics, validation, model listing, inspection, various tests, security audit, snapshot export, log capture, and load/unload actions. Even the testing tools are separated by specific API features (inference, endpoints, tool calling, streaming, structured output), leaving no real ambiguity.
All tools share the lmstudio_ prefix and use snake_case, but there is a mix of bare nouns (status, capabilities, benchmark) and verb_noun compounds (list_models, load_model, test_inference). This is mostly consistent and readable, but not perfectly uniform.
With 18 tools, the server is slightly above the typical well-scoped range, but the breadth is justified by its comprehensive diagnostic and testing mission. The tools cover distinct aspects of local LM Studio management and verification, so the count feels reasonable rather than bloated.
The toolset covers the full lifecycle of interacting with a local LM Studio: listing and inspecting models, loading/unloading, testing core API paths (inference, tool calling, structured output, streaming), health/diagnostics, security auditing, configuration validation, and log capture. No critical dead ends or missing operations are apparent for the stated purpose.