Skip to main content
Glama
dam2452

llmstudio-mcp

by dam2452
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llmstudio-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • mcp-server-lmstudio

      ibukichi-jp
      F
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible clients to use locally running LM Studio models as tools for sending prompts, listing available models, and checking server status. It automatically handles WSL2 networking and follows the currently loaded model without reconfiguration.
      3
      -

    • Ollama MCP Server

      AmandaWood46
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible applications to manage and use local or cloud-hosted models, including listing, pulling, generating, chatting, embeddings, and web search/fetch through a unified tool interface.
      689 npm
      AGPL 3.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct purpose: chat, complete, and embed for inference; list_models, get_model, load_model, unload_model for model management; raw_request as an escape hatch. No functional overlap.

    Naming Consistency5/5

    Consistent verb_noun pattern (e.g., get_loaded_models, list_models, load_model) with simple action verbs for inference (chat, complete, embed). All lowercase with underscores; clear and predictable.

    Tool Count5/5

    9 tools cover the core server management lifecycle: model discovery, loading/unloading, inference, and a raw_request for extensibility. Neither too few nor too many for the domain.

    Completeness4/5

    Covers all essential operations: model listing, loading, inference (chat/complete/embed), and unloading. Missing model download/delete is a minor gap, but raw_request can handle edge cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources