<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Integrations - Category - EONYX Guide</title><link>https://eonyx.tech/guide/categories/integrations/</link><description>Integrations - Category - EONYX Guide</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>eonyx.tech@proton.me (EONYX)</managingEditor><webMaster>eonyx.tech@proton.me (EONYX)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://eonyx.tech/guide/categories/integrations/" rel="self" type="application/rss+xml"/><item><title>EONYX and MCP: connecting external tools</title><link>https://eonyx.tech/guide/eonyx-mcp/</link><pubDate>Tue, 30 Jun 2026 00:00:00 +0300</pubDate><author><name>EONYX</name></author><guid>https://eonyx.tech/guide/eonyx-mcp/</guid><description><![CDATA[<div class="featured-image">
                <img src="/guide/eonyx-mcp/cover.svg" referrerpolicy="no-referrer">
            </div><p><strong>Model Context Protocol (MCP)</strong> is an open standard.<br>
Through it an agent reaches external systems: databases, APIs, trackers, anything.<br>
EONYX ships an MCP client built on the official Go SDK, <code>modelcontextprotocol/go-sdk</code>.<br>
Servers are described in <code>eonyx.json</code>, and their tools appear to the model next to the built-in ones.</p>]]></description></item><item><title>EONYX Hooks: Automation Around Tool Calls</title><link>https://eonyx.tech/guide/eonyx-hooks/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0300</pubDate><author><name>EONYX</name></author><guid>https://eonyx.tech/guide/eonyx-hooks/</guid><description><![CDATA[<div class="featured-image">
                <img src="/guide/eonyx-hooks/cover.svg" referrerpolicy="no-referrer">
            </div><p><strong>Hooks</strong> are shell commands that run <strong>around a tool call</strong>.<br>
One before it, one after it.<br>
They bolt on formatting, auditing and guardrails without touching the agent&rsquo;s code.</p>]]></description></item><item><title>EONYX Headless Mode: Running the Agent Without the TUI</title><link>https://eonyx.tech/guide/eonyx-headless/</link><pubDate>Tue, 19 May 2026 00:00:00 +0300</pubDate><author><name>EONYX</name></author><guid>https://eonyx.tech/guide/eonyx-headless/</guid><description><![CDATA[<div class="featured-image">
                <img src="/guide/eonyx-headless/cover.svg" referrerpolicy="no-referrer">
            </div><p>EONYX also runs <strong>headless</strong>: it does the task and exits.<br>
That is what scripts, pipes and CI need.<br>
Predictable output, JSON events, meaningful exit codes.</p>]]></description></item><item><title>EONYX recipes: practical workflows</title><link>https://eonyx.tech/guide/eonyx-recipes/</link><pubDate>Mon, 18 May 2026 00:00:00 +0300</pubDate><author><name>EONYX</name></author><guid>https://eonyx.tech/guide/eonyx-recipes/</guid><description><![CDATA[<div class="featured-image">
                <img src="/guide/eonyx-recipes/cover.svg" referrerpolicy="no-referrer">
            </div><p>Features are nice.<br>
Seeing them work is better.<br>
A few practical scenarios: how to phrase the task, and which technique to switch on.<br>
The prompts are deliberately plain.</p>]]></description></item></channel></rss>