add-ollama-tool
Skill98 starsChanged 8 months agoApache-2.0View on GitHub
Add Ollama MCP server so the container agent can call local models for cheaper/faster tasks like summarization, translation, or general queries.
- 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★ 31k15% same
- nanocoai/nanoclaw★ 31k15% same
- qwibitai/nanoclaw★ 31k15% same
- microsoft/amplifier-app-nanoclaw★ 546% same
- TomGranot/groupguard★ 315% same
- prathish-ks/isthmus★ 215% same
- breakcafe/picoclaw★ 195% same
- mcarmona1064-cell/clawbridge-codex★ 147% same
- ss2code/nanoclaw-ops★ 115% 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 repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-dingtalkSkill
- add-discordSkill
- add-gmailSkill
- add-parallelSkill
- add-slackSkill
- add-telegramSkill
- add-telegram-swarmSkill
- add-vaspSkill
- add-voice-transcriptionSkill
- add-whatsappSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- qodo-pr-resolverSkill
- setupSkill
- update-matclawSkill
- use-local-whisperSkill
- x-integrationSkill
The file
We split this skill into the rules it gives an agent
11 rules. 2 are common, 4 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read .matclaw/state.yaml. If ollama is in applied_skills, skip to Phase 3 (Configure).
- Common: line 22
Verify Ollama is installed and running on the host:
- Distinctive: line 28
If Ollama is not installed, direct the user to https://ollama.com/download.
- Common: line 30
If no models are installed, suggest pulling one:
- Distinctive: line 42
Run the skills engine to apply this skill's code package.
- Very specific: line 46
If .matclaw/ directory doesn't exist yet:
- Distinctive: line 65
If the apply reports merge conflicts, read the intent files:
- Distinctive: line 118
Run the watcher script for macOS notifications when Ollama is used:
- Very specific: line 146
Verify Ollama is running: ollama list
- Very specific: line 147
Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:11434/api/tags
- Very specific: line 148
If using a custom host, check OLLAMA_HOST in .env
“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.
Tools added:
ollama_list_models— lists installed Ollama modelsollama_generate— sends a prompt to a specified model and returns the response
Phase 1: Pre-flight
Check if already applied
Read .matclaw/state.yaml. If ollama is in applied_skills, skip to Phase 3 (Configure). The code changes are already in place.
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
Run the skills engine to apply this skill's code package.
Initialize skills system (if needed)
If .matclaw/ directory doesn't exist yet:
npx tsx scripts/apply-skill.ts --initApply the skill
npx tsx scripts/apply-skill.ts .claude/skills/add-ollama-toolThis deterministically:
- Adds
container/agent-runner/src/ollama-mcp-stdio.ts(Ollama MCP server) - Adds
scripts/ollama-watch.sh(macOS notification watcher) - Three-way merges Ollama MCP config into
container/agent-runner/src/index.ts(allowedTools + mcpServers) - Three-way merges
[OLLAMA]log surfacing intosrc/container-runner.ts - Records the application in
.matclaw/state.yaml
If the apply reports merge conflicts, read the intent files:
modify/container/agent-runner/src/index.ts.intent.md— what changed and invariantsmodify/src/container-runner.ts.intent.md— what changed and invariants
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
npm run build
./container/build.shBuild must be clean before proceeding.
Phase 3: Configure
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.matclaw # macOS
# Linux: systemctl --user restart matclawPhase 4: Verify
Test via WhatsApp
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.
Monitor activity (optional)
Run the watcher script for macOS notifications when Ollama is used:
./scripts/ollama-watch.shCheck logs if needed
tail -f logs/matclaw.log | grep -i ollamaLook for:
Agent output: ... Ollama ...— agent used Ollama successfully[OLLAMA] >>> Generating— generation started (if log surfacing works)[OLLAMA] <<< Done— generation completed
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: ..."
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.

