LLM Bridge MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LLM Bridge MCP summarize this article using Claude 3.5 Sonnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LLM Bridge MCP
LLM Bridge MCP allows AI agents to interact with multiple large language models through a standardized interface. It leverages the Message Control Protocol (MCP) to provide seamless access to different LLM providers, making it easy to switch between models or use multiple models in the same application.
Features
Unified interface to multiple LLM providers:
OpenAI (GPT models)
Anthropic (Claude models)
Google (Gemini models)
DeepSeek
...
Built with Pydantic AI for type safety and validation
Supports customizable parameters like temperature and max tokens
Provides usage tracking and metrics
Related MCP server: MindBridge MCP Server
Tools
The server implements the following tool:
run_llm(
prompt: str,
model_name: KnownModelName = "openai:gpt-4o-mini",
temperature: float = 0.7,
max_tokens: int = 8192,
system_prompt: str = "",
) -> LLMResponseprompt: The text prompt to send to the LLMmodel_name: Specific model to use (default: "openai:gpt-4o-mini")temperature: Controls randomness (0.0 to 1.0)max_tokens: Maximum number of tokens to generatesystem_prompt: Optional system prompt to guide the model's behavior
Installation
Installing via Smithery
To install llm-bridge-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @sjquant/llm-bridge-mcp --client claudeManual Installation
Clone the repository:
git clone https://github.com/yourusername/llm-bridge-mcp.git
cd llm-bridge-mcpInstall uv (if not already installed):
# On macOS
brew install uv
# On Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# On Windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"Configuration
Create a .env file in the root directory with your API keys:
OPENAI_API_KEY=your_openai_api_key
ANTHROPIC_API_KEY=your_anthropic_api_key
GOOGLE_API_KEY=your_google_api_key
DEEPSEEK_API_KEY=your_deepseek_api_keyUsage
Using with Claude Desktop or Cursor
Add a server entry to your Claude Desktop configuration file or .cursor/mcp.json:
"mcpServers": {
"llm-bridge": {
"command": "uvx",
"args": [
"llm-bridge-mcp"
],
"env": {
"OPENAI_API_KEY": "your_openai_api_key",
"ANTHROPIC_API_KEY": "your_anthropic_api_key",
"GOOGLE_API_KEY": "your_google_api_key",
"DEEPSEEK_API_KEY": "your_deepseek_api_key"
}
}
}Troubleshooting
Common Issues
1. "spawn uvx ENOENT" Error
This error occurs when the system cannot find the uvx executable in your PATH. To resolve this:
Solution: Use the full path to uvx
Find the full path to your uvx executable:
# On macOS/Linux
which uvx
# On Windows
where.exe uvxThen update your MCP server configuration to use the full path:
"mcpServers": {
"llm-bridge": {
"command": "/full/path/to/uvx", // Replace with your actual path
"args": [
"llm-bridge-mcp"
],
"env": {
// ... your environment variables
}
}
}License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
1 toolrun_llmB
Run a prompt through an LLM and return the response.
Inputs: prompt (required), model_name, temperature, max_tokens, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity. The tool's purpose is clear and distinct.
A single tool means naming is trivially consistent. 'run_llm' is descriptive and follows a clear verb_noun pattern.
One tool for an LLM bridge is far too few. Typical servers in this domain include multiple tools for model selection, streaming, or context management.
The server offers only a basic 'run' operation with no supporting tools for model listing, configuration, or advanced features, leaving significant gaps.
Maintenance
Related MCP Connectors
One API key, dozens of capabilities for your AI agent. Zero provider auth.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceFacilitates enhanced interaction with large language models (LLMs) by providing intelligent context management, tool integration, and multi-provider AI model coordination for efficient AI-driven workflows.MIT
- AlicenseCqualityDmaintenanceAn AI router that connects applications to multiple LLM providers (OpenAI, Anthropic, Google, DeepSeek, Ollama, etc.) with smart model orchestration capabilities, enabling dynamic switching between models for different reasoning tasks.3104 npm41MIT
- AlicenseAqualityDmaintenanceEnables AI agents to connect to and chat with multiple LLM models (OpenAI, OpenRouter, custom endpoints) with conversation history management and model switching capabilities.319 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables IDE agents to delegate coding tasks to any LLM provider — cloud APIs like NVIDIA NIM, OpenRouter, Groq, DeepSeek or local Ollama models — through a unified MCP interface.3MIT