Skip to main content
Glama
shanevcantwell

llauncher

by shanevcantwell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llauncher

No user-submitted related servers found.

    Related Servers

    • Bellows

      zaakirio
      A
      license
      A
      quality
      C
      maintenance
      Manages a local fleet of llama.cpp GGUF models, enabling AI agents to discover, start, stop, test, and query evaluation results for llama-server processes.
      6
      9 npm
      MIT

    • 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

    • llmstudio-mcp

      dam2452
      F
      license
      A
      quality
      C
      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
      -

    • Harbor MCP Server

      luke-fairbanks
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover, configure, and manage local development servers. Provides tools for app registration, port allocation, lifecycle control, and log access without manual config editing.
      232 npm
      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

    A3.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: model CRUD, server lifecycle (start/stop/swap/cancel), monitoring (status/logs/metrics/slots), and orphan detection. Even closely related tools like server_metrics and server_slots are well-differentiated by their descriptions and sensitivity levels.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using lowercase snake_case (e.g., add_model, start_server, list_orphans). The naming is predictable and intuitive, with no mixed conventions.

    Tool Count5/5

    With 15 tools, the server covers model configuration, server lifecycle, monitoring, and utility functions like validation. The count is well-scoped for the domain—not too sparse to leave gaps, nor too bloated with redundant tools.

    Completeness5/5

    The tool surface provides complete CRUD for models, full server lifecycle (start, stop, swap, cancel), comprehensive monitoring (status, logs, metrics, slots, orphans), and validation. No obvious gaps prevent an agent from managing llama-server processes effectively.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources