add-ollama-tool

Integrate local Ollama models as MCP tools in containerized agents.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill add-ollama-tool-vincentchong123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-ollama-tool
Source: https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy/tree/main/.claude/skills/add-ollama-tool
Command: npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill add-ollama-tool-vincentchong123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @modelcontextprotocol/sdk, zod.

What problem does it solve?

This skill bridges the gap between cloud-based AI agents and local LLMs, allowing your containerized agent to leverage local compute resources for private, cost-effective, or specialized model inference.

Core Features & Use Cases

  • Local Model Inference: Offload tasks like summarization or code generation to local models running on your host machine.
  • Model Library Management: Optionally pull, delete, and inspect local models directly through the agent interface.
  • Use Case: Use a specialized local model like qwen3-coder to handle sensitive code tasks while keeping the data entirely on your local machine, avoiding cloud API costs and privacy concerns.

Quick Start

Ask your agent to list available ollama models and then use the ollama_generate tool to process a prompt with your chosen model.

Frequently Asked Questions about add-ollama-tool

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

FAQPage Schema
How do I integrate local Ollama models into my containerized AI agent?

This Skill integrates local Ollama models into your containerized agent by registering an MCP server, enabling local model inference, model library management, and secure host-to-container environment variable forwarding.

Can I manage my Ollama model library directly through my agent interface?

Yes, you can manage your Ollama model library directly through the agent interface to optionally pull, delete, and inspect local models, ensuring your containerized agent has access to required inference resources.

Do I need a running Ollama daemon to use local model inference with my agent?

Yes, using local Ollama model inference requires a running Ollama daemon on the host machine and proper registration of the stdio-based MCP server within the agent runner to establish communication.

Why use local Ollama models instead of cloud APIs for code generation tasks?

Use local Ollama models for code generation to keep sensitive code tasks entirely on your local machine, avoiding cloud API costs and privacy concerns while leveraging specialized models like qwen3-coder.

What are the limitations of forwarding host environment variables to a containerized agent?

This approach is limited to environments with a running Ollama daemon on the host and requires proper registration of the stdio-based MCP server within the agent runner to maintain secure, keyless local AI operations.