add-ollama-tool

Integrates an Ollama MCP server so container agents can call local models.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-ollama-tool-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-ollama-tool
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/add-ollama-tool
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-ollama-tool-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @modelcontextprotocol/sdk, zod.

What problem does it solve? Containerized agents normally cannot reach local LLMs running on the host machine. This Skill wires a stdio-based MCP server into the NanoClaw agent container so Claude can offload work to local Ollama models and optionally manage the model library, without threading any credentials. ## Core Features & Use Cases - Local model inference tools: Exposes ollama_list_models and ollama_generate so the agent can list installed models and send prompts to them via the Ollama REST API. - Optional library management: With OLLAMA_ADMIN_TOOLS=true, adds tools to pull, delete, inspect, and list running models on the host daemon. - Guided installation with verification: Copies the MCP server source into the container and host trees, registers it in index.ts, forwards env vars, and validates the wiring with structural tests. - Use Case: You want your agent to summarize long documents cheaply using a local llama3.2 model instead of paid API calls, while keeping the option to pull new models on demand. ## Quick Start Ask the agent to add the Ollama tool so it can list local models and generate responses with them.

Frequently Asked Questions about add-ollama-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let a containerized agent use local Ollama models?

Register a stdio MCP server that wraps the Ollama REST API inside the agent container. The server exposes ollama_list_models and ollama_generate tools, reaching the host daemon through host.docker.internal with a localhost fallback.

How do I enable Ollama model management tools for an agent?

Set OLLAMA_ADMIN_TOOLS=true in the .env file and restart the service. This opt-in flag registers additional tools: ollama_pull_model, ollama_delete_model, ollama_show_model, and ollama_list_running.

Does the Ollama MCP integration require API keys or credentials?

No. Ollama runs locally and is keyless, so there are no credentials to configure. The only settings are OLLAMA_HOST for the daemon base URL and the optional OLLAMA_ADMIN_TOOLS flag.

Why does the agent say Ollama is not installed after setup?

The agent is looking for an ollama CLI inside the container instead of using the MCP tools. Verify the server file exists in the agent-runner source, the ollama entry is registered in the mcpServers object in index.ts, and the container image was rebuilt.

Why does ollama_generate return a model not found error?

The model name must exactly match a name returned by ollama_list_models, including any tag suffix like gemma3:1b. List the installed models first, then pass one of those exact names to the generate call.

What happens when pulling a large Ollama model times out?

The pull tool uses stream:false and blocks until the download completes, so large models over 7B can take several minutes. For very large pulls, run ollama pull directly on the host CLI instead.