MCP alerts and an A2A agent

About the project

Two small experiments from April 2025, days after each standard came out. MCP lets an AI assistant use outside tools: I used it to set crypto price alerts from a chat. A2A lets AI agents talk to each other: I wrote a tiny agent and client by hand to learn how it works.

In April 2025 two agent protocols were days old: MCP, for giving an AI tools, and Google's A2A, for agents talking to each other. I learn new things by building something small with them right away.

These two spikes were my first tries. They aren't finished, but they led straight to mcp-jwt, and then to my MCP work at TermiX.

How it works

1. 1

   Ask for an alert

   In chat: "Tell me when this token hits this price."

2. 2

   MCP tool

   The assistant calls the alert tool with the chat's session, and the alert is saved.

3. 3

   A2A, by hand

   A client finds the agent's card and sends a task; the agent answers by the protocol's rules.

What I did

• Three price-alert tools on top of MCP's weather example: set an alert, list alerts, get the latest price. Alerts are tied to the chat session
• Tried moving that server from local to HTTP with SSE. Three days later mcp-jwt has the working version
• Three days after Google released A2A, a minimal agent and client in plain Node: an agent card and the task method, written by hand without an SDK

Screenshots

To be clear

The weather tools are MCP's tutorial code, and the A2A repo is mostly Google's sample code; only the small agent and client are mine. Neither spike was finished.