gitea_admin/a2a-mcp
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 12 Tags

RSS Feed
  • v0.1.6 45e12324df
    Compare

    release: 0.1.6 — relay notifications/progress to MCP client
    All checks were successful
    build / test (push) Successful in 30s
    Details
    publish / npm (push) Successful in 33s
    Details

    gitea_admin released this 2026-05-16 00:37:58 +00:00 | 10 commits to main since this release

    Long-running upstream skills emit MCP notifications/progress on the SSE
    stream. Without forwarding, the gateway swallows them and the MCP
    client (Claude Code, Cursor) aborts the tools/call on its idle timer
    after ~60s — even though the HTTP stream stays warm.

    Gateway now passes the SDK's extra.sendNotification through to
    UpstreamAgent.callTool. Any non-response frame with a method but no id
    becomes a notification on the client side. Each tools/call carries a
    progressToken (client-supplied or request-id fallback) so the client
    can correlate.

    Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

    Downloads