<?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 iSquiz.com</title><link>https://www.isquiz.com/tags/mcp/</link><description>Recent content in Mcp on iSquiz.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>iSquiz.com</copyright><lastBuildDate>Sat, 11 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.isquiz.com/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>What Model Context Protocol Means for SMB AI Integrations</title><link>https://www.isquiz.com/post/model-context-protocol-smb-integrations/</link><pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.isquiz.com/post/model-context-protocol-smb-integrations/</guid><description>
&lt;p&gt;An AI assistant that can read a company's files, query its database, and check its project tracker is a materially different tool than one that can only answer from what it was trained on — but building that connection has historically meant writing a custom integration for every single pairing of AI tool and data source. The &lt;strong&gt;&lt;a href="https://modelcontextprotocol.io/"&gt;Model Context Protocol&lt;/a&gt;&lt;/strong&gt;, an open standard originated by &lt;a href="https://www.anthropic.com/"&gt;Anthropic&lt;/a&gt;, was built to close that gap: one protocol that lets any compatible AI application talk to any compatible data source or tool, instead of a fresh one-off connector for each combination.&lt;/p&gt;</description></item></channel></rss>