Topic

MCP and agent protocols

The protocols that connect models to tools and to each other. What an MCP server exposes, how clients discover it, and how to secure it.

Model Context Protocol, A2A02 articles04 glossary terms03 platforms
Articles

Read on this topic

Deep dives and guides filed under this topic, newest first.
All articles
Deep dive

What is an AI agent? The loop in code, and where it fails

What is an AI agent? A tested agent loop in TypeScript, run offline against a scripted model, with traces of runaway loops, tool errors, and token growth.

9 min readAgents and frameworks

Guide

What is an MCP server? Build and test one in TypeScript

What is an MCP server? Build a tested TypeScript one with a confirmed write tool, debug it with MCP Inspector, and apply the spec's security requirements.

12 min readMCP and agent protocols

Glossary

Terms you will meet

A2AAgent2Agent protocol
A2A (Agent2Agent) is an open protocol, introduced by Google in April 2025, that lets agents built by different vendors discover each other, exchange tasks, and stream results. MCP connects an agent to tools and data, while A2A connects agents to other agents.
MCPModel Context Protocol
MCP (Model Context Protocol) is an open protocol, introduced by Anthropic in November 2024, that standardizes how AI applications connect to tools and data. A host application runs MCP clients that talk to MCP servers over JSON-RPC, using stdio for local servers or Streamable HTTP for remote ones.
MCP server
An MCP server is a program that exposes tools, resources, and prompts to any MCP-compatible client. Write one server for your API or database, and every MCP host, from coding agents to chat apps, can use it.
Tool callingFunction calling
Tool calling is a model returning a structured request to run a function you defined, with arguments, instead of plain text. Your code runs the function and sends the result back, which is how an agent loop reaches systems outside the model.