P
patruff/ollama-mcp-bridge
Let a local Ollama model call MCP tools
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Install command from the repository
npm install -g @modelcontextprotocol/server-filesystem
Parsed from the README we fetched on 2026-11-06; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npm install -g @modelcontextprotocol/server-filesystem
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npm install -g @modelcontextprotocol/server-filesystem. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# MCP-LLM Bridge
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A TypeScript implementation that connects local LLMs (via Ollama) to Model Context Protocol (MCP) servers. This bridge allows open-source models to use the same tools and capabilities as Claude, enabling powerful local AI assistants.
## Overview
This project bridges local Large Language Models with MCP servers that provide various capabilities like:
Filesystem operations
Brave web search
GitHub interactions
Google Drive & Gmail integration
Memory/storage
Image generation with Flux
The bridge translates between the LLM's outputs and the MCP's JSON-RPC protocol, allowing any Ollama-compatible model to use these tools just like Claude does.
## Current Setup
LLM: Using Qwen 2.5 7B (qwen2.5-coder:7b-instruct) through Ollama
MCPs:
Filesystem operations (@modelcontextprotocol/server-filesystem)
Brave Search (@modelcontextprotocol/server-brave-search)
GitHub (@modelcontextprotocol/server-github)
Memory (@modelcontextprotocol/server-memory)
Flux image generation (@patruff/server-flux)
Gmail & Drive (@patruff/server-gmail-drive)
## Architecture
Bridge: Core component that manages tool registration and execution
LLM Client: Handles Ollama interactions and formats tool calls
MCP Client: Manages MCP server connections and JSON-RPC communication
Tool Router: Routes requests to appropriate MCP based on tool type
### Key Features
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
## Setup
1. Install Ollama and required model:
bash
ollama pull qwen2.5-coder:7b-instruct
2. Install MCP servers:
bash
npm install -g @modelcontextprotocol/server-filesystem
npm install -g @modelcontextprotocol/server-brave-search
npm install -g @modelcontextprotocol/server-github
npm install -g @modelcontextprotocol/server-memory
npm install -g @patruff/server-flux
npm install -g @patruff/server-gmail-drive
3. Configure credentials:
Set BRAVEAPIKEY for Brave Search
Set GITHUBPERSONALACCESSTOKEN for GitHub
Set REPLICATEAPITOKEN for Flux
Run Gmail/Drive MCP auth: node path/to/gmail-drive/index.js auth
For example node C:\Users\patru\AppData\Roaming\npm\nodemodules\@patruff\server-gmail-drive\dist\index.js auth
## Configuration
The bridge is configured through bridgeconfig.json:
MCP server definitions
LLM settings (model, temperature, etc.)
Tool permissions and paths
Example:
json
"mcpServers": {
"filesystem": {
"command": "node",
"args": ["path/to/server-filesystem/dist/index.js"],
"allowedDirectory": "workspace/path"
},
// ... other MCP configurations
},
"llm": {
"model": "qwen2.5-coder:7b-instruct",
"baseUrl": "http://localhost:11434"
## Usage
1. Start the bridge:
bash
npm run start
2. Available commands:
list-tools: Show available tools
Regular text: Send prompts to the LLM
quit: Exit the program
Example interactions:
> Search the web for "latest TypeScript features"
[Uses Brave Search MCP to find results]
## Overview
This project bridges local Large Language Models with MCP servers that provide various capabilities like:
Filesystem operations
Brave web search
GitHub interactions
Google Drive & Gmail integration
Memory/storage
Image generation with Flux
The bridge translates between the LLM's outputs and the MCP's JSON-RPC protocol, allowing any Ollama-compatible model to use these tools just like Claude does.
## Current Setup
LLM: Using Qwen 2.5 7B (qwen2.5-coder:7b-instruct) through Ollama
MCPs:
Filesystem operations (@modelcontextprotocol/server-filesystem)
Brave Search (@modelcontextprotocol/server-brave-search)
GitHub (@modelcontextprotocol/server-github)
Memory (@modelcontextprotocol/server-memory)
Flux image generation (@patruff/server-flux)
Gmail & Drive (@patruff/server-gmail-drive)
## Architecture
Bridge: Core component that manages tool registration and execution
LLM Client: Handles Ollama interactions and formats tool calls
MCP Client: Manages MCP server connections and JSON-RPC communication
Tool Router: Routes requests to appropriate MCP based on tool type
### Key Features
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
## Setup
1. Install Ollama and required model:
bash
ollama pull qwen2.5-coder:7b-instruct
2. Install MCP servers:
bash
npm install -g @modelcontextprotocol/server-filesystem
npm install -g @modelcontextprotocol/server-brave-search
npm install -g @modelcontextprotocol/server-github
npm install -g @modelcontextprotocol/server-memory
npm install -g @patruff/server-flux
npm install -g @patruff/server-gmail-drive
3. Configure credentials:
Set BRAVEAPIKEY for Brave Search
Set GITHUBPERSONALACCESSTOKEN for GitHub
Set REPLICATEAPITOKEN for Flux
Run Gmail/Drive MCP auth: node path/to/gmail-drive/index.js auth
For example node C:\Users\patru\AppData\Roaming\npm\nodemodules\@patruff\server-gmail-drive\dist\index.js auth
## Configuration
The bridge is configured through bridgeconfig.json:
MCP server definitions
LLM settings (model, temperature, etc.)
Tool permissions and paths
Example:
json
"mcpServers": {
"filesystem": {
"command": "node",
"args": ["path/to/server-filesystem/dist/index.js"],
"allowedDirectory": "workspace/path"
},
// ... other MCP configurations
},
"llm": {
"model": "qwen2.5-coder:7b-instruct",
"baseUrl": "http://localhost:11434"
## Usage
1. Start the bridge:
bash
npm run start
2. Available commands:
list-tools: Show available tools
Regular text: Send prompts to the LLM
quit: Exit the program
Example interactions:
> Search the web for "latest TypeScript features"
[Uses Brave Search MCP to find results]
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/patruff-ollama-mcp-bridge/)
- Source
- awesome · https://github.com/patruff/ollama-mcp-bridge
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.