<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on SoloSoft</title><link>https://www.solosoft.dev/tags/tools/</link><description>Recent content in Tools on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP TypeScript SDK: Build Model Context Protocol Servers</title><link>https://www.solosoft.dev/post/mcp-typescript-sdk-2026/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/mcp-typescript-sdk-2026/</guid><description>&lt;p&gt;The Model Context Protocol (MCP) is rapidly becoming the standard way to connect AI agents with external tools, APIs, and data sources. The official TypeScript SDK, maintained by the modelcontextprotocol organization, provides everything developers need to build MCP servers that expose functionality to AI assistants like Claude.&lt;/p&gt;
&lt;p&gt;MCP creates a standardized interface between AI models and the tools they use. Instead of building custom integrations for every AI agent, you build an MCP server once, and any MCP-compatible client can discover and use your tools.&lt;/p&gt;
&lt;h2 id="what-the-sdk-provides"&gt;What the SDK Provides&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Component&lt;/th&gt;
 &lt;th&gt;Description&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Server framework&lt;/td&gt;
 &lt;td&gt;Build MCP servers with tool, resource, and prompt handlers&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Client library&lt;/td&gt;
 &lt;td&gt;Connect to MCP servers from any TypeScript application&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Transport layer&lt;/td&gt;
 &lt;td&gt;Built-in support for stdio and SSE (Server-Sent Events)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Schema validation&lt;/td&gt;
 &lt;td&gt;Type-safe tool definitions with Zod integration&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Authentication&lt;/td&gt;
 &lt;td&gt;OAuth 2.0 and API key support for secure connections&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcp-architecture"&gt;MCP Architecture&lt;/h2&gt;

&lt;figure class="mermaid-wrapper not-prose" role="img" aria-label="Mermaid diagram"&gt;
 &lt;div class="mermaid-container"&gt;
 &lt;pre class="mermaid"&gt;flowchart LR
 A[AI Client&amp;lt;br/&amp;gt;Claude, etc.] --&amp;gt; B[MCP Protocol&amp;lt;br/&amp;gt;JSON-RPC]
 B --&amp;gt; C[MCP Server]
 C --&amp;gt; D[Tool: Calculator]
 C --&amp;gt; E[Tool: Database]
 C --&amp;gt; F[Tool: Web Search]
 C --&amp;gt; G[Resource: Files]
 B --&amp;gt; H[Transport Layer&amp;lt;br/&amp;gt;stdio / SSE]&lt;/pre&gt;
 &lt;script type="application/mermaid"&gt;flowchart LR
 A[AI Client&lt;br/&gt;Claude, etc.] --&gt; B[MCP Protocol&lt;br/&gt;JSON-RPC]
 B --&gt; C[MCP Server]
 C --&gt; D[Tool: Calculator]
 C --&gt; E[Tool: Database]
 C --&gt; F[Tool: Web Search]
 C --&gt; G[Resource: Files]
 B --&gt; H[Transport Layer&lt;br/&gt;stdio / SSE]&lt;/script&gt;
 &lt;/div&gt;
&lt;/figure&gt;&lt;p&gt;The architecture follows a clean client-server pattern. The AI client communicates with the MCP server over JSON-RPC messages, and the server exposes tools and resources that the AI can invoke. The transport layer handles the underlying communication, whether that&amp;rsquo;s subprocess stdio or network SSE.&lt;/p&gt;</description></item></channel></rss>