WAKE Protocol
Define how long-running AI agents hand off state, seal a Black Box audit trail, and respect time-locks when sessions end or operators step away.
Overview
WAKE Protocol is a MCP server for the Operate phase that implements post-mortem succession for AI agents with Black Box capture, handoff, and time-locks.
What is this MCP server?
- WAKE Protocol v2.2.2: post-mortem succession for AI agents
- Black Box pattern for auditable session capture
- Explicit handoff and time-lock concepts for controlled succession
- stdio npm package wake-mcp-server (subfolder wake-mcp-server)
- Documentation site at omodaka9375.github.io/wake/
- Protocol / server version 2.2.2
- npm identifier: wake-mcp-server
- Transport: stdio
Community signal: 3 GitHub stars.
What problem does it solve?
Long-running coding agents lose accountability and recoverable state when sessions end abruptly, leaving the next operator to reconstruct intent from chat scraps.
Who is it for?
Solo builders operating multi-session autonomous agents who need explicit succession, audit-friendly Black Box behavior, and time-gated handoffs.
Skip if: One-shot chat tasks with no continuity requirements, or teams that only need simple conversation export without protocol semantics.
What do I get? / Deliverables
After installing wake-mcp-server, agents can follow WAKE succession steps so handoffs and sealed records persist across session boundaries.
- MCP tools implementing WAKE Protocol succession semantics
- Structured handoff artifacts between agent sessions
- Time-locked release behavior for sensitive successor actions
Recommended MCP Servers
Journey fit
Operate is the canonical shelf because WAKE addresses continuity, succession, and post-mortem capture when agents run in production-like workflows. Iterate covers improving agent reliability, recovery rituals, and operational protocols rather than greenfield feature code.
How it compares
Agent succession and post-mortem MCP protocol, not a logging SaaS integration or a generic memory vector store.
Common Questions / FAQ
Who is io.github.Omodaka9375/wake for?
It is for developers running production-style AI agent workflows who want standardized post-mortem succession, Black Box records, and handoff time-locks via MCP.
When should I use io.github.Omodaka9375/wake?
Use it when agents span multiple sessions or operators and you need governed handoff after failures, context limits, or deliberate session endings.
How do I add io.github.Omodaka9375/wake to my agent?
Install the wake-mcp-server npm package with stdio transport in your MCP configuration, following the wake-mcp-server subfolder project and docs at the WAKE Protocol website.