Discover and explore top open-source AI tools and projects—updated daily.
AlexsJonesServe local LLMs with a TUI
Top 99.0% on SourcePulse
A simple Text User Interface (TUI) designed to streamline the process of serving local Large Language Models (LLMs). It addresses the complexity of managing numerous models scattered across different formats (GGUF, MLX) and inference engines by auto-detecting available backends and model locations, allowing users to launch servers with minimal configuration. This tool is ideal for researchers and power users who frequently experiment with various local LLMs and need a quick, unified way to serve them.
How It Works
llmserve employs a TUI built with Ratatui and Crossterm, presenting a three-panel layout: Sources (model locations), Models (searchable model table), and Serve/Logs (running servers and live output). It automatically discovers installed inference engines like llama-server, KoboldCpp, LocalAI, MLX, Ollama, vLLM, and LM Studio. The application scans specified directories for model files, enabling users to select a model and backend, adjust essential parameters via presets (e.g., context size, GPU layers), and launch servers directly from the interface. A key advantage is the real-time streaming of backend stdout/stderr logs, providing immediate feedback and diagnostics.
Quick Start & Requirements
curl -fsSL https://llmserve.axjns.dev/install.sh | shbrew tap AlexsJones/llmserve && brew install llmservecargo install llmservellama-server, KoboldCpp, LocalAI, MLX, Ollama, vLLM, LM Studio) to be installed and accessible on the system. MLX backend requires Python 3.x on macOS.https://llmserve.axjns.dev/install.sh. Companion project llmfit is available for model suitability analysis.Highlighted Details
.mmproj) for relevant backends.Maintenance & Community
No specific details regarding maintainers, sponsorships, or community channels (like Discord or Slack) are provided in the README.
Licensing & Compatibility
Limitations & Caveats
llmserve functions as a front-end interface and relies on the user having the actual LLM inference backends installed and configured separately. Backends like Ollama, vLLM, and LM Studio are detected but manage their own model registries and cannot serve local files directly through llmserve. The TUI nature makes it less suitable for automated or scripted deployments compared to pure CLI tools.
2 weeks ago
Inactive
ollama