with one click
add-ollama-tool
// Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries.
// Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries.
Show what this AgentLite instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.
Delegate sub-tasks to remote ACP (Agent Client Protocol) peers such as Claude Code or Codex via the built-in acp_* host actions. Use when the user asks to hand work to another agent, wants a second opinion, or needs long / sandboxed execution that shouldn't block this chat.
Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.
Add Discord bot channel integration to AgentLite.
Add Gmail integration to AgentLite. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
| name | add-ollama-tool |
| description | Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries. |
This skill adds a stdio-based MCP server that exposes local Ollama models as tools for the container agent. Claude remains the orchestrator but can offload work to local models.
Tools added:
ollama_list_models — lists installed Ollama modelsollama_generate — sends a prompt to a specified model and returns the responseCheck if container/agent-runner/src/ollama-mcp-stdio.ts exists. If it does, skip to Phase 3 (Configure).
Verify Ollama is installed and running on the host:
ollama list
If Ollama is not installed, direct the user to https://ollama.com/download.
If no models are installed, suggest pulling one:
You need at least one model. I recommend:
ollama pull gemma3:1b # Small, fast (1GB) ollama pull llama3.2 # Good general purpose (2GB) ollama pull qwen3-coder:30b # Best for code tasks (18GB)
git remote -v
If upstream is missing, add it:
git remote add upstream https://github.com/qwibitai/agentlite.git
git fetch upstream skill/ollama-tool
git merge upstream/skill/ollama-tool
This merges in:
container/agent-runner/src/ollama-mcp-stdio.ts (Ollama MCP server)scripts/ollama-watch.sh (macOS notification watcher)container/agent-runner/src/index.ts (allowedTools + mcpServers)[OLLAMA] log surfacing in src/container-runner.tsOLLAMA_HOST in .env.exampleIf the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.
Existing groups have a cached copy of the agent-runner source. Copy the new files:
for dir in data/sessions/*/agent-runner-src; do
cp container/agent-runner/src/ollama-mcp-stdio.ts "$dir/"
cp container/agent-runner/src/index.ts "$dir/"
done
npm run build
./container/build.sh
Build must be clean before proceeding.
By default, the MCP server connects to http://host.docker.internal:11434 (Docker Desktop) with a fallback to localhost. To use a custom Ollama host, add to .env:
OLLAMA_HOST=http://your-ollama-host:11434
launchctl kickstart -k gui/$(id -u)/com.agentlite # macOS
# Linux: systemctl --user restart agentlite
Tell the user:
Send a message like: "use ollama to tell me the capital of France"
The agent should use
ollama_list_modelsto find available models, thenollama_generateto get a response.
Run the watcher script for macOS notifications when Ollama is used:
./scripts/ollama-watch.sh
tail -f logs/agentlite.log | grep -i ollama
Look for:
Agent output: ... Ollama ... — agent used Ollama successfully[OLLAMA] >>> Generating — generation started (if log surfacing works)[OLLAMA] <<< Done — generation completedThe agent is trying to run ollama CLI inside the container instead of using the MCP tools. This means:
container/agent-runner/src/index.ts has the ollama entry in mcpServers./container/build.shollama listdocker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tagsOLLAMA_HOST in .envThe agent may not know about the tools. Try being explicit: "use the ollama_generate tool with gemma3:1b to answer: ..."