Which LLM models does it support?
The bridge works with any Ollama-compatible model. The current setup uses Qwen 2.5 7B (`qwen2.5-coder:7b-instruct`), and future improvements plan to support more Ollama models.
MCP-LLM Bridge
@patruff
Basic information
About MCP-LLM Bridge
Bridge between Ollama and MCP servers, enabling local LLMs to use Model Context Protocol tools
MCP-LLM Bridge config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryMCP-LLM Bridge tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is MCP-LLM Bridge?
A TypeScript implementation that connects local LLMs (via Ollama) to Model Context Protocol (MCP) servers. It translates between an LLM’s outputs and MCP’s JSON‑RPC protocol, letting open‑source models use the same tools and capabilities as Claude while running entirely locally.
How to use MCP-LLM Bridge?
Install Ollama, pull a model (e.g., ollama pull qwen2.5-coder:7b-instruct), and globally install the required MCP servers via npm. Set API keys/tokens in your environment. Create a bridge_config.json for MCP server definitions and LLM settings. Start the bridge with npm run start. Available commands: list‑tools (show available tools), regular text (send prompts), and quit.
Key features of MCP-LLM Bridge
- Multi‑MCP support with dynamic tool routing
- Structured output validation for tool calls
- Automatic tool detection from user prompts
- Robust process management for Ollama
- Detailed logging and error handling
Use cases of MCP-LLM Bridge
- Search the web for recent information (Brave Search MCP)
- Create, read, or modify files and folders (Filesystem MCP)
- Send emails and manage documents (Gmail & Drive MCP)
- Interact with GitHub repositories (GitHub MCP)
- Generate images via Flux (Flux MCP)
Frequently asked questions
What MCP servers are included?
The README lists six: Filesystem, Brave Search, GitHub, Memory, Flux image generation, and Gmail & Drive.
How does tool detection work?
The bridge automatically detects tools based on user input—for example, email addresses trigger Gmail operations, file/folder keywords trigger Drive operations, and search terms are routed to Brave Search.
Where does data live?
All processing runs completely locally with open‑source models; no cloud data transfer is mentioned.
What credentials are required?
Brave Search requires `BRAVE_API_KEY`, GitHub requires `GITHUB_PERSONAL_ACCESS_TOKEN`, Flux requires `REPLICATE_API_TOKEN`, and the Gmail/Drive MCP must be authenticated via `node path/to/gmail-drive/index.js auth`.
More AI & Agents MCP servers
F
fhirHydrant
faulkjOpen-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.
14
Pocket Network Agentic Marketplace: Pay-per-Call APIs
Pocket Network FoundationMCP server for the Pocket Network agentic marketplace: search our catalog of data services and utilities and call them, paying per request in USDC on Base with x402. No account or API key. Search and describe are free; p
Hostinger
hostingerModel Context Protocol (MCP) server for Hostinger API. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server: This opens a browser window to authorize via OAuth. Once app
148
Cartesia MCP
cartesia-aiCartesia MCP is a remote MCP server for Cartesia (https://cartesia.ai) available at https://mcp.cartesia.ai.
AskOne: Live Q&A and Polls
phurynRun free live audience Q&A and polls from your agent: start an AskOne room, add and launch a poll, approve or hide questions and mark them answered, close the room, then read the questions as a FAQ draft and get the resu
Comments