add-ollama-tool
Skill1 starsChanged 6 months agoMITView on GitHub
Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.
- Reads credentials
9 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- nanocoai/nanoclawedited, first seen Nov 15, 2026
- ss2code/nanoclaw-opsedited, first seen Oct 15, 2026
- prathish-ks/isthmusedited, first seen Oct 12, 2026
- gavrielc/nanoclawedited, first seen Oct 8, 2026
- qwibitai/nanoclawedited, first seen Oct 8, 2026
- TomGranot/groupguardedited, first seen Sep 3, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TomGranotSkilladd-anydoc
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Also in 5 projects that use this
TomGranotSkilladd-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Also in 5 projects that use this
qwibitaiSkilladd-iron-proxy
Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.
Also in 4 projects that use this
qwibitaiSkilladd-mattermost
Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.
Also in 4 projects that use this
b1rdmaniaSkillmigrate-memory
Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.
Also in 6 projects that use this
nanocoaiSkilladd-cursor
Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).
Also in 3 projects that use this
- +5 more from TomGranot
- +1 more from qwibitai
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- gavrielc/nanoclaw★ 31k31% same
- nanocoai/nanoclaw★ 31k31% same
- qwibitai/nanoclaw★ 31k31% same
- DingyangLyu/MatClaw★ 9864% same
- microsoft/amplifier-app-nanoclaw★ 596% same
- TomGranot/groupguard★ 331% same
- prathish-ks/isthmus★ 231% same
- breakcafe/picoclaw★ 164% same
- ss2code/nanoclaw-ops★ 132% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- container/AGENTS.mdAGENTS.md
- add-atomic-chat-toolSkill
- add-dashboardSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-ollama-providerSkill
- add-parallelSkill
- add-resendSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- clawSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- manage-channelsSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-clawbridgeSkill
- qodo-pr-resolverSkill
- setupSkill
- update-clawbridgeSkill
- update-skillsSkill
- x-integrationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 2 are common, 4 are distinctive, and 8 are very specific to this project.
2
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Check if container/agent-runner/src/ollama-mcp-stdio.ts exists.
- Common: line 28
Verify Ollama is installed and running on the host:
- Distinctive: line 34
If Ollama is not installed, direct the user to https://ollama.com/download.
- Common: line 36
If no models are installed, suggest pulling one:
- Very specific: line 54
If upstream is missing, add it:
- Distinctive: line 74
If the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.
- Very specific: line 107
If the user wants management tools, add to .env:
- Distinctive: line 113
If they decline (or don't answer), do not add the variable — management tools will be disabled by default.
- Very specific: line 142
If OLLAMA_ADMIN_TOOLS=true was set, tell the user:
- Distinctive: line 150
Run the watcher script for macOS notifications when Ollama is used:
- Very specific: line 179
Verify Ollama is running: ollama list
- Very specific: line 180
Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tags
- Very specific: line 181
If using a custom host, check OLLAMA_HOST in .env
- Very specific: line 193
Ensure OLLAMA_ADMIN_TOOLS=true is set in .env and the service was restarted after adding it.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Ollama Integration
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, and can optionally manage the model library directly.
Core tools (always available):
ollama_list_models— list installed Ollama models with name, size, and familyollama_generate— send a prompt to a specified model and return the response
Management tools (opt-in via OLLAMA_ADMIN_TOOLS=true):
ollama_pull_model— pull (download) a model from the Ollama registryollama_delete_model— delete a locally installed model to free disk spaceollama_show_model— show model details: modelfile, parameters, and architecture infoollama_list_running— list models currently loaded in memory with memory usage and processor type
Phase 1: Pre-flight
Check if already applied
Check if container/agent-runner/src/ollama-mcp-stdio.ts exists. If it does, skip to Phase 3 (Configure).
Check prerequisites
Verify Ollama is installed and running on the host:
ollama listIf 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)
Phase 2: Apply Code Changes
Ensure upstream remote
git remote -vIf upstream is missing, add it:
git remote add upstream https://github.com/other2368-byte/clawbridge-agent.gitMerge the skill branch
git fetch upstream skill/ollama-tool
git merge upstream/skill/ollama-toolThis merges in:
container/agent-runner/src/ollama-mcp-stdio.ts(Ollama MCP server)scripts/ollama-watch.sh(macOS notification watcher)- Ollama MCP config in
container/agent-runner/src/index.ts(allowedTools + mcpServers) [OLLAMA]log surfacing insrc/container-runner.tsOLLAMA_HOSTin.env.example
If the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.
Copy to per-group agent-runner
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/"
doneValidate code changes
pnpm run build
./container/build.shBuild must be clean before proceeding.
Phase 3: Configure
Enable model management tools (optional)
Ask the user:
Would you like the agent to be able to manage Ollama models (pull, delete, inspect, list running)?
- Yes — adds tools to pull new models, delete old ones, show model info, and check what's loaded in memory
- No — the agent can only list installed models and generate responses (you manage models yourself on the host)
If the user wants management tools, add to .env:
OLLAMA_ADMIN_TOOLS=trueIf they decline (or don't answer), do not add the variable — management tools will be disabled by default.
Set Ollama host (optional)
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:11434Restart the service
launchctl kickstart -k gui/$(id -u)/com.clawbridge # macOS
# Linux: systemctl --user restart clawbridgePhase 4: Verify
Test inference
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.
Test model management (if enabled)
If OLLAMA_ADMIN_TOOLS=true was set, tell the user:
Send a message like: "pull the gemma3:1b model" or "which ollama models are currently loaded in memory?"
The agent should call
ollama_pull_modelorollama_list_runningrespectively.
Monitor activity (optional)
Run the watcher script for macOS notifications when Ollama is used:
./scripts/ollama-watch.shCheck logs if needed
tail -f logs/clawbridge.log | grep -i ollamaLook for:
[OLLAMA] >>> Generating— generation started[OLLAMA] <<< Done— generation completed[OLLAMA] Pulling model:— pull in progress (management tools)[OLLAMA] Deleted:— model removed (management tools)
Troubleshooting
Agent says "Ollama is not installed"
The agent is trying to run ollama CLI inside the container instead of using the MCP tools. This means:
- The MCP server wasn't registered — check
container/agent-runner/src/index.tshas theollamaentry inmcpServers - The per-group source wasn't updated — re-copy files (see Phase 2)
- The container wasn't rebuilt — run
./container/build.sh
"Failed to connect to Ollama"
- Verify Ollama is running:
ollama list - Check Docker can reach the host:
docker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tags - If using a custom host, check
OLLAMA_HOSTin.env
Agent doesn't use Ollama tools
The agent may not know about the tools. Try being explicit: "use the ollama_generate tool with gemma3:1b to answer: ..."
ollama_pull_model times out on large models
Large models (7B+) can take several minutes. The tool uses stream: false so it blocks until complete — this is intentional. For very large pulls, use the host CLI directly: ollama pull <model>
Management tools not showing up
Ensure OLLAMA_ADMIN_TOOLS=true is set in .env and the service was restarted after adding it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

