MCP: How AI Agents Use Tools

mcpprotocoltools

An AI model is only as useful as the tools it can access. The Model Context Protocol (MCP) is an open standard that gives AI agents a universal way to discover, connect to, and use external tools and data sources.

The Tool Problem

Before MCP, every AI agent framework had its own way of defining tools. OpenAI function calling worked one way, Anthropic tool use worked another, LangChain had its own abstractions. If you built a tool for one, you had to rebuild it for the others.

MCP standardizes this. A tool built once, as an MCP server, works with any MCP-compatible agent. The protocol handles discovery, schema negotiation, invocation, and response formatting.

How MCP Works

MCP uses a client-server architecture. The AI agent (client) connects to MCP servers that expose tools. Each server describes its capabilities — what tools it offers, what parameters they accept, what they return. The agent can then invoke those tools as needed during a conversation or task.

The key insight is separation of concerns: the AI model handles reasoning and planning, while MCP servers handle execution. The model decides what to do; the tools do it.

MCP Meets x402

Here's where it gets interesting for agent commerce. An MCP server can expose a "send cookies" tool that, under the hood, makes an x402-paid API call. The agent sees a tool. The tool handles the payment. The cookies show up at someone's door.

This layering is powerful. The agent doesn't need to understand x402 or USDC or blockchain transactions. It just calls a tool called send_cookies with a name and address. The MCP server handles the rest — constructing the request, processing the 402 response, making the payment, confirming the order.

The Composable Agent Stack

MCP is the tool layer. x402 is the payment layer. Together, they let agents do useful things in the real world without custom integrations for every service. An MCP server for Agent Cookies can be shared, reused, and composed with other tools.

Want an agent that monitors your calendar and sends cookies to friends on their birthdays? That's an MCP calendar tool plus an MCP cookie tool plus a little bit of LLM reasoning. No custom code required.

The building blocks are here. We just need to keep stacking them.

More from the Bakery

What Is x402? The Payment Protocol That Lets Agents Pay

The HTTP 402 status code was reserved for "Payment Required" in 1997. Nearly three decades later, x402 finally puts it to work — letting AI agents pay for things over the web.

Why Your AI Should Send You Cookies

AI agents are great at research, scheduling, and writing emails. But the most human thing they can do might be ordering a box of cookies for someone you care about.

Agentic Wallets: How Coinbase Gave AI Agents Money

Coinbase's Agentic Wallet lets AI agents hold and spend crypto autonomously. Here's how it works, why it's secure, and what it means for the machine economy.