Skip to main content
Glama
TMHSDigital

Local AI MCP

Official
by TMHSDigital

Related Servers

Alternatives to Local AI MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Discovers local model runtimes such as Ollama, LM Studio, and LocalAI, and exposes their endpoint metadata to MCP clients like Copilot.
      3
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      16 npm
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.
      -
    • 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
      -
    • 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

    TDQS

    A4.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct operation: model management (unload, load, list, pull, remove, info), system information (list_providers, health_check, system_resources), analysis (fit_check, benchmark, suggest_model, search_available), and inference (complete, embed). No two tools have overlapping purposes.

    Naming Consistency4/5

    Tool names predominantly follow a verb_noun pattern (unload_model, list_providers, pull_model). Some names like model_info, system_resources, and benchmark are noun-heavy or single-verb but still clear and readable. Consistent snake_case throughout.

    Tool Count5/5

    With 16 tools, the server is well-scoped for its domain. It covers model lifecycle, system diagnostics, analysis, and inference without being bloated or sparse.

    Completeness5/5

    The tool set covers the full lifecycle: pull, load, unload, remove, list, info, and inference (complete, embed). It also includes system checks (health, resources, fit), search, recommendations, and benchmarks. No obvious gaps for the stated purpose of local AI model management and inference.

    Maintenance

    ActivityStale
    ResponsivenessNo issues