local-llm-mcp
Related Servers
Alternatives to local-llm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows Claude Code to offload mechanical tasks such as summarization, classification, and drafting to a local LLM, reducing API costs while keeping Claude in control of complex reasoning and quality review.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that delegates mechanical tasks like summarization, classification, extraction, and drafting to a local Llama.cpp LLM, serving as a cost-optimization layer while Claude handles reasoning and quality control.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that bypasses Claude's context by routing file processing to local or cloud AI, saving token costs. It reads files from disk and returns distilled results without Claude seeing the raw content.1-
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects Claude to local Ollama models, enabling offloading of simpler tasks to save Claude tokens.716-
- AlicenseAqualityDmaintenanceMCP server that enables cloud models (like Gemini/Claude) to delegate coding tasks to a local llama.cpp server, preserving cloud usage limits through an AI-powered code review loop.61MIT
- AlicenseAqualityDmaintenanceAn MCP server that offloads bulk coding tasks to local LLMs, allowing Claude Code to delegate repetitive work like boilerplate generation and code polishing while preserving its context for complex reasoning.101MIT
TDQS
Scored across 4 tools
Most tools have distinct purposes: local_digest reads files and returns only the result, local_map processes each file separately, local_ask is a free-form query without file input, and local_status checks the LM Studio state. However, local_digest and local_map could be confused as both involve file processing with instructions, though descriptions clarify the difference.
All tool names follow a consistent pattern: 'local_' prefix followed by a descriptive verb in lowercase snake_case (digest, map, ask, status). No mixing of conventions or unexpected variations.
Four tools is well-scoped for a local LLM server. It covers file processing (digest and map), free-form queries (ask), and system status (status). This is neither too sparse nor too heavy for the domain.
The tool set covers the main interactions with a local LLM: processing files (digest, map), asking questions (ask), and checking status (status). Minor gaps exist, such as a tool to load/unload models or access raw file content, but these may be outside the intended scope.