<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Mcp - Sonny</title><link>https://sonny.sh/tags/mcp/</link><description>Recent content on Mcp</description><generator>Hugo 0.139.4</generator><language>en-us</language><lastBuildDate>Sat, 24 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sonny.sh/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Servers</title><link>https://sonny.sh/docs/mcp/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://sonny.sh/docs/mcp/</guid><category>mcp</category><category>tools</category><category>integrations</category><description> MCP Servers Share link Share this section Permalink Share via Twitter LinkedIn Facebook Model Context Protocol lets Sonny call tools hosted by another process — a database bridge, an internal ticketing tool, a packet-capture appliance, another agent framework — over a small JSON-RPC protocol. Instead of teaching Sonny one integration at a time, you point it at a server that already exposes the API you need.</description></item><item><title>MCP Configuration</title><link>https://sonny.sh/docs/mcp/configuration/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://sonny.sh/docs/mcp/configuration/</guid><category>mcp</category><category>configuration</category><category>reference</category><description> MCP Configuration Share link Share this section Permalink Share via Twitter LinkedIn Facebook Where the files live Share link File Location User sidecar config mcp.yaml in the profile config directory — $XDG_CONFIG_HOME/sonny when set, otherwise the platform-native location Project chain .sonny/mcp.yaml in every directory from the cwd up to the filesystem root Allowlist mcp.allowlist.yaml, in the same profile config directory as the sidecar config --mcp-config &amp;lt;path&amp;gt; on sonny run, sonny mcp list, sonny tools list and sonny recipe resolve overrides the user sidecar path for that invocation only. It does not move the project chain or the allowlist.</description></item><item><title>MCP Trust Model</title><link>https://sonny.sh/docs/mcp/trust-model/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://sonny.sh/docs/mcp/trust-model/</guid><category>mcp</category><category>security</category><category>reference</category><description> MCP Trust Model Share link Share this section Permalink Share via Twitter LinkedIn Facebook A configured MCP server is not an approved MCP server. Configuration says what exists; approval decides what runs. Two gates sit between them, and both apply to every surface that enumerates tools — a TUI tab, a headless run, a sub-agent, sonny mcp list --connect, sonny tools list --mcp-config and sonny recipe resolve --connect. A surface that can only list tools is not a way around either gate.</description></item><item><title>MCP Server Catalog</title><link>https://sonny.sh/docs/mcp/servers/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://sonny.sh/docs/mcp/servers/</guid><category>mcp</category><category>reference</category><description> MCP Server Catalog Share link Share this section Permalink Share via Twitter LinkedIn Facebook Ten MCP servers ship under the sonny.sh/mcp/ namespace. Each is its own Go module in its own private repository. The sonny.sh/mcp/&amp;lt;name&amp;gt; pages provide machine-readable go-import metadata for authorized consumers. Browser visitors stay on the public documentation site. These modules are commercial software; see Licensing and access .</description></item></channel></rss>