<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sse on NicoLabs</title>
		<link>http://blog.hellonico.info/tags/sse/</link>
		<description>Recent content in Sse on NicoLabs</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 27 Jul 2026 19:50:00 +0900</lastBuildDate>
		
			<atom:link href="http://blog.hellonico.info/tags/sse/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building a Zero-Dependency MCP Client &amp; Server Natively in Coni</title>
				<link>http://blog.hellonico.info/posts/coni/native-mcp/</link>
				<pubDate>Mon, 27 Jul 2026 19:50:00 +0900</pubDate>
				<guid>http://blog.hellonico.info/posts/coni/native-mcp/</guid>
				<description>&lt;p&gt;The &lt;strong&gt;Model Context Protocol (MCP)&lt;/strong&gt; is rapidly becoming the gold standard for connecting Large Language Models to external tools and data sources. Historically, if you wanted to build an MCP client or server, you needed to reach for heavy, bloated SDKs in Node.js or Python, dealing with complex asynchronous state and dependency hell.&lt;/p&gt;&#xA;&lt;p&gt;We thought: &lt;em&gt;What if we could do it entirely natively in Coni?&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;In this post, we’re going to walk through how we brought a complete, zero-dependency MCP Client and Server directly into the Coni standard library (&lt;code&gt;mcp.coni&lt;/code&gt;). It’s fast, highly concurrent, and ridiculously easy to use.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
