Our take
Activeregular commits- Activity
- 41
- Community
- 66
- Issues
- 53
- Pull requests
- 51
+2 stars in the last 16 days
This is a useful, actively updated discovery index for the growing Google A2A ecosystem, though it is a directory rather than a verified compatibility catalog.
Good fit if
- You need to discover A2A server examples, hosted services, frameworks, or utilities across different categories.
- You want a quick way to compare projects by language and local or cloud scope before reviewing their source repositories.
- You can assess each listing independently, since the directory organizes projects but does not establish their quality or compatibility.
Look elsewhere if
- You need a single A2A implementation to install, deploy, or operate. This repository collects links rather than providing a server.
- You need a comprehensive protocol compatibility or maintenance certification for each entry. The README does not describe such a verification process.
- You need a packaged release or installation instructions for this directory. The README provides neither.
All health signals
| Last commit | 2026-10-17 (2 days ago) |
|---|---|
| Commits, last 90 days | 50 |
| Releases, last 12 months | 0 |
| Contributors | 60 (top contributor: 55% of commits) |
| Issues closed, last 90 days | 2 |
| Pull requests merged, last 90 days | 24 (typically merged in 1 day) |
| Project age | 19 months |
Checked on 2026-10-20 with the GitHub API.
Overview
awesome-a2a is a curated directory of server implementations for Google's Agent2Agent (A2A) protocol. A2A standardizes how AI agents discover capabilities, submit tasks, track progress, and receive results; this list helps developers find implementations and services to build interoperable agent systems.
Entries are grouped by service category, with language and deployment-scope markers where provided. The directory spans hosted and local projects and multiple programming languages, alongside frameworks and utilities for building or connecting A2A agents. It is a discovery resource, not an A2A server or installable software package.
Key Features
- Groups server listings into categories such as location, business, financial, search, communication, developer, knowledge, data, and travel services.
- Highlights official Google A2A sample implementations, including examples using Google ADK, LangGraph, and CrewAI.
- Uses a legend to identify implementation languages and whether a service is local, cloud-hosted, or embedded.
- Includes separate sections for frameworks and utilities, covering tools for building, testing, and connecting agents.
- Links to listed repositories and, for some hosted services, their live agent cards.
- Provides links to A2A tutorials, the protocol community, and contribution guidance.
Use Cases
- An agent developer can search for an existing A2A service, such as a mapping or search agent, before building an integration from scratch.
- A team evaluating A2A can compare sample servers and frameworks to identify a starting point for a proof of concept.
- A framework maintainer can use the language and scope markers to find related implementations and potential interoperability examples.
- A developer building an A2A service can submit a relevant listing to make it easier for others to discover.
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Browse the README and follow a listing to its project or agent card. For protocol concepts and setup examples, start with the Google A2A documentation.
Considerations
- The project is active, with regular recent commits and merged pull requests, but it has no release in the past year. Since this is a curated list, changes are delivered through repository updates rather than packaged releases.
- Contributions are spread across many contributors, with no measured concentration around one person. Recent issue closures have been limited, so do not assume open questions or reports will be resolved quickly.
- The README does not state that entries are tested, continuously checked, or guaranteed to remain available. Verify a project's protocol version, maintenance, and service status before depending on it.
- The list includes hosted services as well as local implementations. Review each linked project's requirements, terms, and deployment model separately.
Found this useful?
Share it with someone who would like awesome-a2a.