add-ollama-tool
Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.
Profile →npx skills add nanocoai/nanoclaw --skill add-ollama-tool --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Add Ollama Integration This skill adds a stdio-based MCP server that exposes local [Ollama](https://ollama.com) models as tools for the container agent. Claude remains the orchestrator but can offload work to local models served by the Ollama daemon on the host, and can optionally manage the model library directly. Ollama runs locally and is keyless — there are no credentials to thread; the only configuration is the daemon's base URL. Core tools (always available): - `ollama_list_models` — list installed models with name, size, and family (`GET /api/tags`) - `ollama_generate` — send a prompt to a specified model and return the response (`POST /api/generate`) Management tools (opt-in via `OLLAMA_ADMIN_TOOLS=true`): - `ollama_pull_model` — pull (download) a model from the Ollama registry (`POST /api/pull`) - `ollama_delete_model` — delete a locally installed model to free disk space (`DELETE /api/delete`) - `ollama_show_model` — show model details: modelfile, parameters, and architecture info (`POST /api/show`) - `ollama_list_running` — list models currently loaded in memory with memory usage and processor type (`GET /api/ps`) The skill ships the MCP server source (and its tests) i
- Phase 1: Pre-flight
- Check if already applied
- Check prerequisites
- Phase 2: Apply Code Changes
- Copy the skill's source and tests into both trees
- Register the MCP server in the agent-runner
- Forward host env vars into the container
- Surface [OLLAMA] log lines at info level
- Add env-var stubs to .env.example
- Validate code changes
- Phase 3: Configure
- Enable library-management tools (optional)
- Set Ollama host (optional)
- Restart the service
curl -s http://127.0.0.1:11434/api/tags | head 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) Container (Bun) tree — the MCP server and the registration wiring test cp $S/ollama-mcp-stdio.ts container/agent-runner/src/ollama-mcp-stdio.ts cp $S/ollama-registration.test.ts container/agent-runner/src/ollama-registration.test.ts Host (Node) tree — the env-forwarding helper and the wiring test cp $S/ollama-env.ts src/ollama-env.ts cp $S/ollama-wiring.test.ts src/ollama-wiring.test.ts
What does the add-ollama-tool skill do?
Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.
How do I install it?
Run `npx skills add nanocoai/nanoclaw --skill add-ollama-tool --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.