A
AWP
v0.1.0-alpha
Live network · protocol node active

The event channel
that completes MCP

MCP lets an active agent call a service. AWP lets that service deliver a later event back and resume the correct local session. Two directions, one continuous workflow.

Get started View source
Agent nodeID: 0x4f...a2
ASYNC_SIGNAL
MCP_CONTEXT
AWP providerlatency: 12ms
12,847 events delivered
01 / COMPLEMENT
AWP does not replace MCP

Two directions.
One agent workflow.

MCP handles what an agent needs while it is active. AWP handles what happens after that turn is over.

MCP · NOW

Agent → Provider

The active agent calls tools, reads resources, and starts work through MCP.

  • Request now
  • Agent initiated
  • Active session
AWP · LATER

Provider → Agent session

The same provider delivers the result later and wakes the right local session through AWP.

  • Event later
  • Provider initiated
  • Session resumed
02 / ONE CONTINUOUS LOOP

The turn can end.
The workflow doesn’t.

AWP carries the result across the gap between an MCP call and a later external event.

01

MCP call

Agent asks a provider to start work.

02

Turn ends

The local agent session becomes inactive.

03

Work completes

The provider receives a result or external change.

04

AWP event

Provider delivers to its outbound client connection.

05

Session resumes

Local AWP routes the event to the correct runtime.

MCPstarts the work
AWPbrings the result back
03 / ARCHITECTURE

Provider-owned endpoints.
One local client.

Every MCP product operates its own AWP endpoint beside its existing service. Your local daemon connects outward to each provider and keeps runtime session IDs on your device.

1:Nclient to providers
0inbound ports
100%runtime IDs local
EVENT DELIVERY TRACEHEALTHY
01
Client connects outwardwss://provider.example/awp
02
Local sessions bindprovider + opaque session_id
03
Provider delivers laterevent.deliver / at-least-once
04
Correct runtime resumeslocal mapping / event.ack
01

Provider responsibility

Expose an authenticated AWP endpoint, retain offline events, deliver to the correct device and handle acknowledgements.

02

Local client responsibility

Maintain outbound connections, map opaque AWP sessions to local runtimes, resume the right agent and preserve its permissions.

04 / PRINCIPLES

Designed to sit beside MCP

Asynchronous return channel

Providers can deliver a result after the original MCP turn has ended—without polling or keeping the agent busy.

Provider-owned topology

Each product exposes its own AWP endpoint beside MCP. There is no shared central broker in the middle.

Local identity boundary

Runtime session IDs and the mapping to provider-scoped AWP sessions stay on the user’s device.

05 / QUICKSTART

Add the return path to your agent.

Install the local AWP client, connect a provider, and let completed work find its way back to the right session.

awp — zsh
$ curl -LsSf https://awp.manifestro.io/install.sh | sh
✓ platform detected: darwin/arm64
✓ SHA-256 checksum verified
✓ installed to ~/.local/bin/awp

AWP is ready.
06 / ROADMAP

Protocol status

A focused companion to MCP today, an interoperable provider ecosystem tomorrow.

CURRENT

Q1—Q2 Alpha

  • Go multi-provider client
  • Provider-scoped session routing
  • Codex CLI wake adapter
  • Reconnect and event acknowledgements
NEXT

Stable release

  • Pairing and credential lifecycle
  • Cross-runtime conformance suite
  • Additional runtime adapters
  • Protocol governance process
A

MCP starts the work.
AWP brings it back.

Add asynchronous delivery without replacing the tools you already use.

Add AWP to MCP