<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ai agents on The NNDI Blog</title><link>https://blog.nndi.cloud/tags/ai-agents/</link><description>Recent content in ai agents on The NNDI Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>hello@nndi.cloud (NNDI)</managingEditor><webMaster>hello@nndi.cloud (NNDI)</webMaster><lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.nndi.cloud/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Steps to connect AI Agents to your application via the Model Context Protocol (MCP)</title><link>https://blog.nndi.cloud/posts/ai/steps-to-add-mcp-to-applications/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><author>hello@nndi.cloud (NNDI)</author><guid>https://blog.nndi.cloud/posts/ai/steps-to-add-mcp-to-applications/</guid><description>It&amp;rsquo;s been over a year since the Model Context Protocol (MCP) was introduced as a way to integrate AI. MCP enables you to connect AI Agents and LLMs to perform actions on your system or fetch data that can be analyzed or used by AI.
MCP unlocks a lot of potential for automation as you can now initiate operations by giving instructions in natural language.
The MCP protocol, though in it&amp;rsquo;s infancy, has already seen massive adoption from the industry as a way to supercharge AI Agents with capabilities that do not come built-in and grant them access to information that may be siloed behind closed off or legacy systems.</description></item></channel></rss>