Skip to main content
Glama

Related Servers

Alternatives to lmstudio

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients to manage, run, and interact with local or cloud LLM models through exposed tools for listing, pulling, generating, chatting, embeddings, and web search/fetch. Supports Claude Desktop, Cline, and hybrid local/cloud setups.
      812 npm
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.
      2
      264 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code and Codex to delegate persistent review or isolated write-mode implementation tasks to locally installed Claude Code or Codex runtimes, then inspect progress, approve or deny individual permission requests, and continue the same native conversation. It also lists live model catalogues, lets callers follow up on saved conversations, and can run independently via its bundled CLI.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      22
      516 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and lifecycle stages, especially the model, session, task, and server management groups. The main overlap is among prompt-sending tools (chat, session_send, task_start), but descriptions make their differences clear enough for an agent.

    Naming Consistency3/5

    All names use snake_case and are readable, but conventions are mixed: some are verb_noun (load_model, list_models), others are noun_verb (session_send, task_status) or noun_noun (model_defaults, download_status). The inconsistency is noticeable but not chaotic.

    Tool Count3/5

    Twenty tools is on the heavy side and sits in the borderline 16-25 range for a single MCP server. The domain is broad (server, models, downloads, sessions, tasks, embeddings), so most tools earn their place, but the set feels larger than necessary.

    Completeness4/5

    The surface covers most core workflows: model download/load/unload/list, chat and sessions, background tasks, embeddings, and server control. Minor gaps remain, such as no clear download cancellation or model deletion operation, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues