MCP-LLM Bridge

@patruff

リポジトリ

基本情報

カテゴリ

AI とエージェント

ライセンス

MIT

トランスポート

stdio

作者

patruff

MCP-LLM Bridge について

Bridge between Ollama and MCP servers, enabling local LLMs to use Model Context Protocol tools

MCP-LLM Bridge の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

MCP-LLM Bridge のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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)

よくある質問

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.

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`.

「AI とエージェント」の他のコンテンツ

treg.to

Jason Zhou

OpenRouter for tools & data — 3,028 APIs for your agent, one token, pay per call. treg.to is a remote MCP server at https://treg.to/mcp/ that gives an agent 3,028 ready-to-call API endpoints across 82 platforms: SEO and

q-ring

I4cTime

Quantum-inspired keyring for AI coding agents. Secure secrets with superposition, entanglement, tunneling, and teleportation — CLI + 44 MCP tools.

InsumerAPI

Wallet auth for AI agents: send a blockchain wallet and conditions, get a signed yes or no across 37 chains, never the balance. Hosted at https://api.insumermodel.com/mcp with no key (10 tools), or run locally with npx -

Hostinger

hostinger

Model 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

fhirHydrant

faulkj

Open-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.