add-ollama-tool

Add a local Ollama MCP server for model listing and generation.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill add-ollama-tool-spyqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-ollama-tool
Source: https://github.com/spyqs/nanoclaw-email-imap/tree/main/.claude/skills/add-ollama-tool
Command: npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill add-ollama-tool-spyqs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It lets the containerized agent use locally installed Ollama models, avoiding the need to route every task through remote APIs and reducing latency and cost for tasks like summarization and translation.

Core Features & Use Cases

  • Adds an Ollama MCP server: Exposes Ollama models to the container agent via stdio MCP so the agent can call them as tools.
  • Enables model discovery and generation: Provides ollama_list_models to enumerate installed models and ollama_generate to run prompts through a chosen model.
  • Supports practical workflows: Use it when you want the agent to answer questions using local models, such as turning long text into summaries, translating content, or performing general reasoning without external calls.

Quick Start

In your Claude Code prompt, run the install/configuring workflow by telling the user to add the Ollama MCP tool integration and then ask the agent to answer using the local tools.

Frequently Asked Questions about add-ollama-tool

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

FAQPage Schema
How do I enable local Ollama model inference in a container agent?

To enable local Ollama model inference, you add a local Ollama MCP server to the container agent. This exposes installed models via stdio MCP, allowing the agent to call them as tools for generating responses using host-local inference.

What is the benefit of using local Ollama tools for AI tasks instead of remote APIs?

Using local Ollama tools reduces latency and cost by avoiding routing every task through remote APIs. It enables host-local inference for practical workflows like summarization, translation, and general question answering without external calls.

How do I configure an MCP server to list installed Ollama models?

You configure an MCP server by wiring MCP server registration and tool definitions in the agent-runner. This provides the `ollama_list_models` tool to enumerate installed models and `ollama_generate` to run prompts through a chosen model.

Can I use Ollama with a containerized agent for text summarization and translation?

Yes, you can use Ollama with a containerized agent for text summarization and translation. The integration exposes local models as tools via stdio MCP, enabling the agent to perform these practical workflows using host-local inference.

Do I need to update cached runner sources when adding an Ollama MCP server?

Yes, you need to update per-group cached runner sources when adding an Ollama MCP server. This step is part of wiring the MCP server registration and tool definitions, and must be validated with a clean build.

Why does my container agent still route to remote APIs after adding local model inference?

If the container agent still routes to remote APIs, the MCP server registration may be incomplete. You must ensure the agent-runner is updated, per-group cached runner sources are refreshed, and the integration is validated with a clean build.