MCP-Ollama Client
About
Lightweight MCP client that uses a local Ollama LLM to query multiple MCP servers defined in config.json
Details
- License
- MIT license
Explore
| Feature | Notes |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Local LLM first | Default model is qwen3:14b, but any function‑calling model that Ollama exposes will work. No cloud keys required. |
| Multi‑server out‑of‑the‑box | Postgres, filesystem, or your own MCP servers can run side‑by‑side; all are defined in config.json. |
| Collision‑free tool names | Tools are exposed as <server>.<tool> so names never clash. |
---
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP-Ollama ClientCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
| Component | Version tested |
| ------------- | -------------------------------------------|
| Python | ≥ 3.12 |
| Ollama | ≥ 0.8.0 |
| MCP server(s) | Anything that supports stdio transport |
---
uv venv
source .venv/bin/activate
uv pip sync # or: uv pip install -r uv.lock
{
"llm": {
"model": "qwen3:14b",
"temperature": 0.7,
"max_tokens": 2048
},
"mcpServers": {
"postgres": {
"command": "postgres-mcp",
"args": ["--access-mode=restricted"],
"env": {
"DATABASE_URI": "postgresql://user:pass@localhost:5432/db"
}
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/mnt/smbshare/"
]
}
}
}
Keys under mcpServers become prefixes (postgres., filesystem.).
Each server starts as its own stdio subprocess.
Add or remove servers without touching client.py.
Everything stays local, everything is configurable in one file.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp-ollama client": {
"MCP-Ollama-Client": {
"command": "uv",
"args": [
"venv"
]
}
}
}
}McpServers
{
"MCP-Ollama-Client": {
"command": "uv",
"args": [
"venv"
]
}
}Small command‑line chat client that
1. Runs entirely offline with a local LLM via Ollama
2. Talks to any number of Model‑Context‑Protocol (MCP) servers, all declared in one config.json
At start‑up the client launches every server, fetches their tool schemas, prefixes tool names (postgres., filesystem., …) and gives the merged list to the model.
The LLM decides which server to call for each user request.
---
Features
| Feature | Notes |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Local LLM first | Default model is qwen3:14b, but any function‑calling model that Ollama exposes will work. No cloud keys required. |
| Multi‑server out‑of‑the‑box | Postgres, filesystem, or your own MCP servers can run side‑by‑side; all are defined in config.json. |
| Collision‑free tool names | Tools are exposed as <server>.<tool> so names never clash. |
---
Requirements
| Component | Version tested |
| ------------- | -------------------------------------------|
| Python | ≥ 3.12 |
| Ollama | ≥ 0.8.0 |
| MCP server(s) | Anything that supports stdio transport |
---
Quick start
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
