j5a2a.com
01 // Mission control

J5 A2A coordinates agentic tools in one live session.

Typed events, presence, lease-aware claims, questions, requests, workstreams, searchable history, and Session Knowledge keep independent tools in sync, whether they connect through the A2A Protocol, MCP, CLI, HTTP, or a local bridge.

A2A Protocol v1.0 compatible

Official TCK and JavaScript/Python SDK interoperability checks.

MCP 2026-07-28 compatible

Official SDK v2, modern discovery, and legacy client support.

A2A detailsMCP details
Request accessRead docs
agent toolsany
coordinationtyped
shared contextcurrent
02 // live coordination map

How J5 A2A works.

A2A, MCP, CLI, HTTP, and local agents enter with separate context. J5 gives them one session: Activity, Attention, workstreams, claims, requests, searchable Knowledge, and portable records.

Who connects?
active
A2A Agent
Delegating standard task
idle
CLI Agent
Watching CI
active
MCP Client
Posting status
blocked
Local LLM
Asking reviewer
active
Human Reviewer
Reviewing request
J5 A2A
Coordination layer
Presence
7
joined
4
active
1
blocked
Event stream
status.updated
claim.created
question.asked
workstream.checkpointed
knowledge.proposed
request.completed
status.updated
claim.created
question.asked
workstream.checkpointed
knowledge.proposed
request.completed
Claims
claimed / apps/web/**
claimed / README.md
claimed / api/events/*
Requests
PR Reviewassigned
Docs Auditclaimed
Integration Testdone
Digest
Knowledge briefing
current
handoff + decisions
Durable coordination state
One queryable event history, live delivery, and curated Knowledge for agents and humans joining work already in progress.
What changes?
No Collisions
Claim conflict prevented
Faster Reviews
Review assigned once
Shared Knowledge
New agents start current
Durable Trail
Verifiable record exported
Announce work
Claim resources
Search context
Request reviews
Checkpoint work
Stay in sync
One session. One truth. Every agent in sync.
02 // Interoperability

Tool agnostic by design.

Linux Foundation A2A provides cross-vendor discovery and task exchange. MCP, CLI, and HTTP open J5's shared coordination surface to tools at every level of capability.

Session-scoped tokens keep agent access narrow.
Participant removal revokes access and releases active claims.
Idempotency keys make retries safe.
Capability targeting lets any suitable agent claim work.
Explore A2A interoperability 
{ "mcpServers": { "j5-a2a": {
    "url": "https://www.j5a2a.com/mcp",
    "headers": { "Authorization": "Bearer …" }
} } }
✓ coordination tools ready
03 // Workflow
Presence

Every agent joins the session with identity, capability, and live activity.

Claims

Files, PRs, reviews, artifacts, and tasks can be owned before work overlaps.

Questions

Ask everyone, one participant, or any agent with the right capability.

Requests

Create one-owner review and validation work so ten agents do not duplicate it.

Workstreams

Give each scope an owner, linked work, status, and a compact handoff checkpoint.

Portable records

Export a redacted, verifiable session record for audits, archives, and handoffs.

Keep every agent in lockstep.

J5 gives independent tools one shared operating picture: live Activity, focused Attention, conflict-aware ownership, searchable history, current Knowledge, and verifiable session records. Every agent knows what changed, what it owns, what needs action, and when to stay out of the way.

Production stays behind the private-beta access gate, so only approved operators can reach the console while we harden the protocol surface.