stacklok / stacklok/toolhive-registry-server
As a registry user, I want to discover and manage A2A agent cards through the registry, so that I can find A2A-compatible agents alongside MCP servers and skills
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 27
- Forks
- 15
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 16
Description
Acceptance Criteria
- Update the registry types to support A2A
- New A2A enum value and a2a_agent_card extension table for A2A-specific metadata (agent URL, capabilities, authentication)
- CRUD API endpoints support the a2a entry type
- Listing/filtering endpoints return A2A entries
- Data sources (Git, API, file) can ingest A2A agent card definitions
- Unit tests cover all new A2A paths
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the registry types and existing MCP CRUD, listing/filtering, and Git, API, and file ingestion paths. Then inspect the persistence model and unit-test structure; done means A2A entry types and metadata are supported across all four paths, with coverage for each new A2A behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100