The Blog

AI Workflows vs Agents: A Developer's Guide to Architectural Decisions

Integrating MCP Into Your Product: Why Your SaaS Needs Tool-Calling AI

In Part 1, we understood why MCP matters. In Part 2, we built a universal MCP client. In Part 3, we created the agentic layer. Now let's talk about why this matters for your product — and how to actually integrate it.test

Building an AI Agent with MCP: The ChatManager Deep Dive (Part 3)

In Part 1, we learned that MCP = Function Calling + Standardization. We saw how MCP servers expose tools and how clients communicate with them through JSON-RPC messages. In Part 2, we built a UniversalMCPClient that connects to any MCP server (stdio, SSE, or Streamable HTTP), discovers available tools, and executes them. But here’s what we haven’t solved yet: How do you make an AI that automatically decides which tools to use?(using mcp client)

MCP Client Tutorial: Connect to Any MCP Server in 5 Minutes (mcp_client Part2)

You’ve read about MCP. You understand it’s “Function Calling + Standardization.” You’ve seen dozens of MCP servers on GitHub — Gmail, Slack, databases, weather APIs. Claude Desktop and Cursor have MCP client built-in.

MCP = Function Calling + Standardization (Just for Tools) Mcp_client Part1

The Equation That Changes Everything