Skip to main content
Glama
portertech

LM Studio MCP Server

by portertech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LM Studio MCP Server

No user-submitted related servers found.

    Related Servers

    • subforge-mcp

      nathan-vm
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to interact with models running locally in LM Studio, including listing loaded models, chatting with per-session history, and loading models into memory with user consent.
      25 npm
      MIT

    • Ollama MCP Server

      etnlbck
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with locally running Ollama models through chat, generation, and model management operations. Supports listing, downloading, and deleting models while maintaining conversation history for interactive sessions.
      363 npm
      MIT

    • ai-model-selector-mcp

      barrymister
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with structured access to metadata for 76+ AI models across Ollama, Claude, and OpenRouter, enabling capability queries, compatibility checks, model comparisons, and task-based recommendations.
      12 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health_check for connectivity, list_models vs list_loaded_models for different sets, get_model_info for details on a loaded model, and load/unload for lifecycle management. No ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_model_info, list_choices, load_model, unload_model). health_check deviates as a noun phrase but is conventional and understandable. Overall consistent.

    Tool Count5/5

    With 6 tools covering connectivity, listing, loading/unloading, and info query, the count is well-scoped for the domain of model management without bloat or deficiency.

    Completeness4/5

    The set covers core model lifecycle (load, unload, list, info) and connectivity. Minor gaps like model deletion or parameter configuration are not critical for common agent tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources