Skip to main content
Glama
didou92i

lmstudio-local

by didou92i
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lmstudio-local

No user-submitted related servers found.

    Related Servers

    • llmstudio-mcp

      dam2452
      F
      license
      A
      quality
      D
      maintenance
      MCP 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.
      9
      1
      -

    • local-llm-mcp

      Qinlupfu
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      MIT

    • Ollama MCP Server

      DanielleMorita48217
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients to manage and run local or cloud LLMs, generate completions and embeddings, and perform web search/fetch through exposed tools.
      689 npm
      AGPL 3.0

    • Ollama MCP Server

      hcho43
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible applications to manage, run, chat with, and generate embeddings from local or cloud LLM models, and to perform web search and content fetching via cloud APIs.
      689 npm
      AGPL 3.0
    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/5.0

    Scored across 28 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources