add-atomic-chat-tool

Integrate local OpenAI-compatible model servers into containerized agents via MCP.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tharunramagiri/bookoraaagent --skill add-atomic-chat-tool-tharunramagiri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-atomic-chat-tool
Source: https://github.com/tharunramagiri/bookoraaagent/tree/main/.claude/skills/add-atomic-chat-tool
Command: npx skills add https://github.com/tharunramagiri/bookoraaagent --skill add-atomic-chat-tool-tharunramagiri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @modelcontextprotocol/sdk, zod, typescript.

What problem does it solve?

This skill bridges the gap between your containerized AI agent and local, privacy-focused models running on your desktop, allowing you to offload tasks to local hardware without exposing data to external APIs.

Core Features & Use Cases

  • Local Model Access: Exposes models running in the Atomic Chat desktop app as MCP tools for your agent.
  • Tool-Based Inference: Enables the agent to list available local models and generate responses using specific local LLMs.
  • Use Case: Use this to perform private, high-volume summarization or translation tasks using a local model like Llama 3.2, keeping your sensitive data entirely on your machine.

Quick Start

Ask the agent to use atomic chat to tell me the capital of France using the available local models.

Frequently Asked Questions about add-atomic-chat-tool

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

FAQPage Schema
How do I connect a local LLM to a containerized AI agent using MCP?

Local LLM connection to a containerized AI agent via MCP requires mapping OpenAI-compatible host API endpoints to agent-accessible tools. This skill forwards environment variables and registers an MCP server to enable secure communication between the host desktop application and the isolated agent container.

Can I use Atomic Chat models for private inference without exposing data to external APIs?

Atomic Chat models support private inference without external API exposure by running entirely on local desktop hardware. The skill bridges containerized agents to local models, enabling high-volume tasks like summarization or translation while keeping sensitive data completely on the machine.

What's the best way to expose local model servers as agent tools in a containerized environment?

Exposing local model servers as agent tools requires registering them through the Model Context Protocol. This skill maps host-side OpenAI-compatible endpoints to isolated agent tools, facilitating secure local inference execution within the containerized environment.

Does this local model integration work with any OpenAI-compatible server?

Local model integration works with OpenAI-compatible model servers running in the Atomic Chat desktop application. It requires environment variable forwarding and MCP server registration to map the host-side API endpoints to the containerized agent environment.

Why do I need environment variable forwarding for local LLM inference in a container?

Environment variable forwarding is required for local LLM inference in a container to establish secure communication between the host desktop application and the isolated agent. It enables the MCP server registration needed to map local API endpoints to agent-accessible tools.

What are the limitations of using local models for agent inference instead of external APIs?

Local model inference limitations include dependency on host desktop hardware performance and the need for OpenAI-compatible server compatibility. The approach restricts execution to the Atomic Chat environment, requiring MCP server registration and environment variable forwarding for containerized agent access.