What is the default model and does it require cloud access?
The default model is `qwen3:14b`. Any function‑calling model that Ollama exposes will work. No cloud keys are required; everything runs locally.
@Nagharjun17
Basic information
Lightweight MCP client that uses a local Ollama LLM to query multiple MCP servers defined in config.json
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"MCP-Ollama-Client": {
"command": "uv",
"args": [
"venv"
]
}
}
}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.
MCP-Ollama Client is a command‑line chat client that runs entirely offline with a local LLM via Ollama and connects to any number of Model Context Protocol (MCP) servers declared in a single config.json. It is designed for developers who want to use local function‑calling models together with MCP tools.
Clone the repository, set up a Python ≥ 3.12 virtual environment with uv, install dependencies, pull a local model with ollama pull qwen3:14b, edit the model name and server settings in config.json, then run uv run client.py. At startup the client launches every MCP server, aggregates their tool schemas with server‑name prefixes (e.g. postgres.*, filesystem.*), and presents the merged list to the LLM.
config.json fileThe default model is `qwen3:14b`. Any function‑calling model that Ollama exposes will work. No cloud keys are required; everything runs locally.
Python ≥ 3.12, Ollama ≥ 0.8.0, and any MCP servers that support **stdio** transport.
Tools are exposed as `<server>.<tool>` (for example `postgres.list_schemas`, `filesystem.read_file`) so names never clash, even when different servers provide tools with the same name.
Data stays entirely local. Servers are defined in `config.json` under the `mcpServers` key; you can add or remove servers by editing that file without touching `client.py`.
Each MCP server is started as its own **stdio** subprocess. No network transport is used between the client and the servers.
Official MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Anycast CDN, Video CDN and Media CDN

KissCode is the world's first relationship network where AI agents and people meet. Connect your agent over MCP: it gets a profile, meets other agents and real people, chats, sends virtual gifts, goes on dinner and movie
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.

FLORA is a remote MCP server available at https://agents.flora.ai. The FLORA MCP lets users generate, organize, and iterate on visual assets — hero images, moodboards, lifestyle shots, promo graphics — directly from a co
HeyLead: AI agent for LinkedIn outreach. Finds the right people, writes in your voice, follows up and handles replies, from Claude Code, Cursor, any MCP client or a web dashboard.
Comments