<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API Integration on AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/api-integration/</link><description>Recent content in API Integration on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/api-integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Registering and Discovering Tools: Making Your MCP Services Visible</title><link>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/registering-and-discovering-tools/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/registering-and-discovering-tools/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid AI architects! In our previous chapter, we explored the fascinating world of Tool Schemas, learning how to precisely define the capabilities of an AI agent&amp;rsquo;s external tools. You crafted clear, unambiguous blueprints for what your tools can do. But what&amp;rsquo;s the use of a beautifully designed tool if no one knows it exists?&lt;/p&gt;
&lt;p&gt;This chapter is all about making your amazing tools visible and accessible to AI agents and other services. We&amp;rsquo;ll dive into the critical processes of &lt;strong&gt;tool registration&lt;/strong&gt; and &lt;strong&gt;tool discovery&lt;/strong&gt; within the Model Context Protocol (MCP) ecosystem. Think of it like publishing your tool&amp;rsquo;s &amp;ldquo;yellow pages&amp;rdquo; entry, allowing agents to find and understand how to interact with your services. By the end of this chapter, you&amp;rsquo;ll be able to register your custom MCP tools and understand how AI agents can discover and utilize them, including how to enrich tool definitions with UI resources for more dynamic interactions.&lt;/p&gt;</description></item><item><title>Fortifying Your Integrations: Permissions, Authorization, and Security Best Practices</title><link>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/security-permissions-authorization/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/security-permissions-authorization/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid AI architects! In our previous chapters, we&amp;rsquo;ve explored the Model Context Protocol (MCP), learned how to define powerful tools with detailed schemas, and understood how AI agents can discover and interact with these tools. We&amp;rsquo;ve built the mechanisms for intelligence to flow, but there&amp;rsquo;s a crucial piece missing: control.&lt;/p&gt;
&lt;p&gt;Imagine you&amp;rsquo;ve built an amazing MCP tool that can process financial transactions. Would you want just &lt;em&gt;any&lt;/em&gt; AI agent, or &lt;em&gt;any&lt;/em&gt; user interacting with that agent, to be able to access and execute every function of that tool? Absolutely not! This is where the critical concepts of permissions, authorization, and robust security practices come into play.&lt;/p&gt;</description></item></channel></rss>