<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Local on Vibe Coding</title><link>https://vibecoding.rest/tags/local/</link><description>Recent content in Local on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/local/index.xml" rel="self" type="application/rss+xml"/><item><title>Filesystem</title><link>https://vibecoding.rest/mcp-servers/filesystem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/filesystem/</guid><description>&lt;p&gt;The Filesystem server exposes a sandboxed slice of your local disk to an agent — reading, writing, listing, and searching files within directories you explicitly allow.&lt;/p&gt;&#10;&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;&#10;&lt;p&gt;It&amp;rsquo;s one of the original reference MCP servers, and the clearest example of the protocol&amp;rsquo;s core promise: instead of every agent vendor writing its own file-access layer, any MCP-compatible client can use this one server.&lt;/p&gt;</description></item></channel></rss>