"Integrating Claude Desktop with a Local LLM using the LMStudio API" matching MCP servers:

Enables delegating mechanical or high-volume subtasks to a local LLM through an MCP tool, letting the assistant query the local model without using its own output tokens for content.

A thin MCP server that delegates lightweight tasks from Claude Code or any MCP-compatible client to local or cloud LLMs via LiteLLM, supporting models like Ollama and cloud APIs as subagents.

Enables a cloud orchestrator to query a local Ollama model over Tailscale or a LAN as a side-channel for drafts, summaries, and other helper output, with tools to list available models and to redact text. Answers leaving the server are passed through output-only DLP that masks card numbers, IBANs, emails, phone numbers, API keys, and similar secrets before they reach the cloud.

Enables coding agents like Claude Code and Codex to offload boilerplate generation, summarization, and other bounded text tasks to local or cheap cloud LLMs, keeping the frontier agent in charge of judgment and code edits.

MCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.

A bidirectional MCP bridge that lets Claude Desktop and Claude Code collaborate on a build with no human in the execution loop.

MCP server that delegates Claude Code subagents to alternative backends such as local models, DeepSeek, or AWS Bedrock, while keeping your Claude Code orchestrator session intact.

Enables LLMs to capture desktop screenshots and control the mouse and keyboard on Linux, including Wayland, through MCP.

MCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.

Local-first MCP server that enables multiple Claude agents to coordinate through a shared message bus with SQLite persistence and real-time clock anchoring.

A local-first LLM routing MCP server that keeps sensitive data on your own models, with fail-closed privacy and manager-worker delegation, exposing route and complete tools to any MCP client.

A local MCP gateway that unifies multiple LLM providers, API keys, routing, and multi-model discussions into a single tool surface.

Blind multi-model councils with anonymous LLM seats and direct 1:1 chat as a local MCP server. Enables asking one question to get independent answers from multiple model CLIs, then blind scoring and reveal.

Enables multiple local AI desktop applications to exchange MCP messages and collaborate through a shared JSONL room file, with role-based routing, history, and audit session tools.

Enables a primary agent to offload bounded, high-volume analysis of explicitly selected workspace files to an auxiliary LLM through a single read-only tool, returning text, Markdown, JSON, or unified-diff output with token usage while retaining all planning, verification, and edits.

Routes your AI tasks to the best available model across 20+ providers — automatically selecting based on task type, budget, and subscription pressure. Supports text, image, video, and audio with built-in cost optimization and fallback chains.

A Model Context Protocol (MCP) gateway for running Claude Code, Codex, Gemini, Grok, and Mistral (Vibe) CLIs from one MCP endpoint, with durable async jobs, session continuity, cache-aware prompting, observability, and personal-appliance setup tooling. Why developers try it: one local MCP endpoint for cross-LLM validation, multi-agent coding workflows.

MCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.

Enables AI agents to interact with multiple LLM providers (OpenAI, Anthropic, Google, DeepSeek) through a standardized interface, making it easy to switch between models or use multiple models in the same application.

MCP server for the LLM Wiki Chrome extension that exposes bounded browser automation tools (shared tabs, accessibility snapshots, screenshots, clicks, typing, etc.) with explicit user consent and strict typing, enabling local agents to interact with specific web pages via a native messaging relay.