LLM Bridge MCP

What is 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.

How to use LLM Bridge MCP?

Configure API keys in a .env file (or pass them as environment variables) and then add a server entry to your Claude Desktop or Cursor configuration. The server exposes a single tool, run_llm, which accepts a prompt, optional model name (default openai:gpt-4o-mini), temperature, max tokens, and system prompt.

Key features of LLM Bridge MCP

• Unified interface to OpenAI, Anthropic, Google, and DeepSeek models.
• Built with Pydantic AI for type safety and validation.
• Supports customizable temperature and max tokens parameters.
• Provides usage tracking and metrics.
• Simple single-tool API: run_llm.

Use cases of LLM Bridge MCP

• Let an AI agent query multiple LLM providers from one integration.
• Switch models in a running application without reconfiguration.
• Compare outputs from GPT, Claude, Gemini, and DeepSeek in the same workflow.
• Build a multi-model assistant that can choose the best model per task.

FAQ from LLM Bridge MCP

Which LLM providers are supported?

OpenAI (GPT models), Anthropic (Claude models), Google (Gemini models), and DeepSeek.

How do I install LLM Bridge MCP?

You can install it automatically via Smithery (npx -y @smithery/cli install @sjquant/llm-bridge-mcp --client claude) or manually by cloning the repository and following the manual installation steps.

How do I configure API keys?

Create a .env file in the root directory with keys like OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, and DEEPSEEK_API_KEY. Alternatively, pass them as environment variables in the MCP server configuration.

How do I use LLM Bridge MCP with Claude Desktop or Cursor?

Add a server entry to your Claude Desktop configuration or .cursor/mcp.json file, specifying the command uvx and the package name llm-bridge-mcp, along with the required API keys.

What does the "spawn uvx ENOENT" error mean?

It means the system cannot find the uvx executable in your PATH. Find the full path to uvx using which uvx (macOS/Linux) or where.exe uvx (Windows), then update your MCP server configuration to use that full path.