AgendaForge Event Operations
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://mcp.agendaforge.app/mcp
· transport MCP
Event reads event-reads
Read events, sessions, agendas, speakers, contacts, sponsors, forms, submissions, registration, and email activity.
eventssessionsspeakersread-onlyEvent search event-search
Search accessible organization records and contacts, with optional event scope.
searchcontactseventsApproval-gated operations approval-gated-operations
Propose changes and communications that take effect only after a person approves them in AgendaForge.
writehuman-approvaleventsMedia upload media-upload
Request a one-time event logo or cover upload link after organizer approval.
mediauploadhuman-approval2026-10-29 from https://agendaforge.app/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.