llauncher
Related Servers
Alternatives to llauncher
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManages a local fleet of llama.cpp GGUF models, enabling AI agents to discover, start, stop, test, and query evaluation results for llama-server processes.618 npmMIT
- AlicenseBqualityBmaintenanceExposes a local llama.cpp server's chat, completion, tokenization, model listing, and health endpoints as tools, enabling MCP hosts such as Claude Code to delegate prompts and text processing to a local model.5MIT
- AlicenseAqualityCmaintenanceEnables 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.9MIT
- AlicenseNot gradedqualityCmaintenanceManages dev server lifecycles for AI coding agents, providing structured process awareness, health checks, and JSON outputs to prevent panic cycles.MIT
- AlicenseAqualityBmaintenanceConnects agentic platforms to one or more local or networked LM Studio instances, exposing chat, embeddings, model listing, health, and pool-status tools. Provides intelligent load balancing, automatic failover with circuit breaking, role-based routing, and a daemon mode with a real-time web dashboard and HTTP/SSE endpoints.51MIT
- FlicenseAqualityDmaintenanceMCP 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.91-
TDQS
Scored across 15 tools
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.
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.
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.
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.