Skip to main content
Glama
Ka1y0

lmstudio-mcp

by Ka1y0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lmstudio-mcp

No user-submitted related servers found.

    Related Servers

    • Msty Local Ops by vega-llc

      Msty Local Opsofficial

      vega-llc
      A
      license
      A
      quality
      A
      maintenance
      A 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.
      4
      MIT

    • local-mcp-toolbox

      chriswayneh
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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.
      MIT

    • UVG Local MCP Server

      Anggelie
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local text analysis, statistical calculations, and system information retrieval via the Model Context Protocol over stdio.
      -

    • embrace-raw-readonly

      nano-step
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only interaction with official Embrace MCP tools while preserving full structured response data, including session aggregates and detailed logs, crashes, network, and spans, through a local stdio server.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 18 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources