A2E Protocol

Agent-to-Entity Protocol

Discover which MCP serves a given entity.

"Book a table at Le Petit Zinc"
         │
         ▼
    ┌─────────┐
    │   A2E   │  →  "Le Petit Zinc uses mcp.zenchef.com"
    └─────────┘
         │
         ▼
    ┌─────────┐
    │   MCP   │  →  Execute reservation
    └─────────┘

The Problem

MCP directories list servers by capabilities:

"ZenChef is an MCP with reservations capability"

But agents need to know:

"Which MCP serves Le Petit Zinc?"

A2E solves this.

How It Works

Entities publish a JSON file at /.well-known/a2e.json:

{
  "a2e": "1.0",
  "entity": {
    "domain": "lepetitzinc.fr",
    "name": "Le Petit Zinc",
    "category": "restaurant"
  },
  "mcps": [
    {
      "endpoint": "https://mcp.zenchef.com",
      "capabilities": ["reservations", "availability", "menu"]
    }
  ]
}

That's it. Agents can now discover how to interact with any entity.

Documentation

Full Specification - Complete protocol documentation
JSON Schema - For validation
Examples - Sample a2e.json files

Ecosystem

Protocol	Purpose
MCP	How agents use tools
A2A	How agents talk to each other
A2E	How agents discover which MCP serves an entity

Get Started

Use A2E Index to generate your a2e.json file and make your entity discoverable by AI agents.