<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mcp on toorun.dev</title><link>https://toorun.dev/tags/mcp/</link><description>Recent content in mcp on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://toorun.dev/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Explained: Model Context Protocol for AI Assistants, Local Tools, and Embedded Work</title><link>https://toorun.dev/posts/mcp-model-context-protocol-explained-ai-tools-embedded/</link><pubDate>Sat, 31 Oct 2026 10:00:00 +0100</pubDate><guid>https://toorun.dev/posts/mcp-model-context-protocol-explained-ai-tools-embedded/</guid><description>MCP Explained: Model Context Protocol for AI Assistants, Local Tools, and Embedded Work MCP (Model Context Protocol) is an open protocol that lets an AI assistant call tools and read data from programs you run. The model stays in the chat app. The MCP server is a local (or remote) process that exposes tools such as “read this folder”, “query this database”, or “run this command”.
It is not a neural-network format, not a Linux kernel interface, and not something you flash onto a microcontroller.</description></item></channel></rss>