<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent Integration Guide on SAM</title><link>https://sam-mesh.dev/docs/integrations/</link><description>Recent content in Agent Integration Guide on SAM</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://sam-mesh.dev/docs/integrations/index.xml" rel="self" type="application/rss+xml"/><item><title>Exposing Inference Services: OpenRouter</title><link>https://sam-mesh.dev/docs/integrations/openrouter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/openrouter/</guid><description>&lt;h1 id="exposing-inference-services-openrouter">Exposing Inference Services: OpenRouter&lt;/h1>
&lt;p>In the Sovereign Agent Mesh (SAM), large language models (LLMs) and foundational model APIs are exposed across the mesh as &lt;strong>Inference Services&lt;/strong>, not just standard Model Context Protocol (MCP) servers. This allows your deployed agents to dynamically discover, route, and consume inference capabilities directly through the P2P network, utilizing SAM&amp;rsquo;s decentralized authorization (Biscuit) for access control.&lt;/p>
&lt;p>This guide explains how to expose &lt;a href="https://openrouter.ai/">OpenRouter&lt;/a> as an inference service to the mesh, completely shielding your API keys from external peers.&lt;/p></description></item><item><title>Integrating SAM with Claude Code</title><link>https://sam-mesh.dev/docs/integrations/claude-code/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/claude-code/</guid><description>&lt;p>You can connect your &lt;code>sam-node&lt;/code> to &lt;a href="https://claude.com/claude-code">Claude Code&lt;/a> as a remote MCP server, giving Claude Code agents the ability to discover and invoke tools across the SAM mesh.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>&lt;code>sam-node&lt;/code> exposes a standard Model Context Protocol (MCP) server over HTTP Server-Sent Events (SSE). Claude Code is a generic MCP client, so once the server is registered its tools — &lt;code>discover_remote_services&lt;/code>, &lt;code>find_remote_tools&lt;/code>, &lt;code>describe_remote_tool&lt;/code>, and &lt;code>call_remote_tool&lt;/code> — are surfaced directly to your agent.&lt;/p></description></item><item><title>Integrating SAM with Claude Desktop</title><link>https://sam-mesh.dev/docs/integrations/claude-desktop/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/claude-desktop/</guid><description>&lt;p>You can connect your &lt;code>sam-node&lt;/code> to the &lt;a href="https://claude.com/download">Claude Desktop&lt;/a> app as an MCP server. Unlike &lt;a href="./claude-code/">Claude Code&lt;/a>, Claude Desktop has its own configuration and does &lt;strong>not&lt;/strong> read Claude Code&amp;rsquo;s MCP settings.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Claude Desktop&amp;rsquo;s &lt;code>claude_desktop_config.json&lt;/code> natively launches &lt;strong>stdio&lt;/strong> MCP servers (a local command). &lt;code>sam-node&lt;/code> exposes an &lt;strong>SSE&lt;/strong> server, so you bridge the two with &lt;a href="https://www.npmjs.com/package/mcp-remote">&lt;code>mcp-remote&lt;/code>&lt;/a> — a small stdio-to-remote proxy that Claude Desktop launches locally and that connects to your node&amp;rsquo;s SSE endpoint.&lt;/p></description></item><item><title>Integrating SAM with Google Antigravity</title><link>https://sam-mesh.dev/docs/integrations/antigravity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/antigravity/</guid><description>&lt;p>You can connect your &lt;code>sam-node&lt;/code> to Google Antigravity as an MCP server. By exposing the SAM Model Context Protocol (MCP) server to Antigravity, the agent can dynamically discover tools hosted by other peers in the mesh, describe them, and execute them to solve tasks.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Antigravity natively supports Streamable HTTP MCP servers via the &lt;code>serverUrl&lt;/code> configuration. Since &lt;code>sam-node&lt;/code> implements the Streamable HTTP transport, you can connect it directly without any bridge.&lt;/p></description></item><item><title>Integrating SAM with OpenClaw</title><link>https://sam-mesh.dev/docs/integrations/openclaw/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/openclaw/</guid><description>&lt;p>You can seamlessly integrate your &lt;code>sam-node&lt;/code> as a remote MCP server in &lt;a href="https://openclaw.ai">OpenClaw&lt;/a>, allowing your agents to dynamically discover and invoke tools across the mesh.&lt;/p>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>By configuring your &lt;code>sam-node&lt;/code> as an MCP server, you enable your OpenClaw agents to access the P2P mesh, discovering tools from remote nodes and executing services as if they were local.&lt;/p>
&lt;h2 id="configuration">Configuration&lt;/h2>
&lt;p>To bridge your local &lt;code>sam-node&lt;/code> into your OpenClaw agent runtime, use the &lt;code>openclaw mcp&lt;/code> CLI. Ensure your node is running and identify the API token configured in your &lt;code>sam-node&lt;/code> launch arguments.&lt;/p></description></item><item><title>Running a Gemini AI Agent on the Mesh</title><link>https://sam-mesh.dev/docs/integrations/gemini/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sam-mesh.dev/docs/integrations/gemini/</guid><description>&lt;p>This tutorial demonstrates how to connect a local AI Agent powered by Google Gemini (using the official &lt;code>google-genai&lt;/code> SDK) to your local SAM node.&lt;/p>
&lt;p>By exposing the SAM Model Context Protocol (MCP) server to Gemini, the agent can dynamically discover tools hosted by other peers in the mesh, describe them, and execute them to solve tasks.&lt;/p>
&lt;hr>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>Python 3.10+&lt;/strong>: Ensure Python is installed on your host.&lt;/li>
&lt;li>&lt;strong>SAM Node Running&lt;/strong>: A local SAM node should be running and enrolled on the testnet (see the &lt;a href="../quickstart/">Quick Start Guide&lt;/a>).&lt;/li>
&lt;li>&lt;strong>Gemini API Key&lt;/strong>: Obtain an API key from Google AI Studio and export it:
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">&lt;span class="nb">export&lt;/span> &lt;span class="nv">GEMINI_API_KEY&lt;/span>&lt;span class="o">=&lt;/span>&lt;span class="s2">&amp;#34;your-api-key-here&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
&lt;/ol>
&lt;hr>
&lt;h2 id="1-setup-the-python-client">1. Setup the Python Client&lt;/h2>
&lt;p>Go to the &lt;code>sam-mcp-python&lt;/code> directory in the repository:&lt;/p></description></item></channel></rss>