push_context
Set a top-level key and broadcast it
How to use it
Project documentation lists push_context for the P2PA MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install P2PA
npm install -g p2paOther tools in P2PA (25)
Publish your role, capabilities and status so peers can route work to you
Ask one agent a question, get a correlation id to match the reply
Block until a peer acts, then return what they did
Recent concurrent updates — already settled, informational
Take a lease directly, for work that is not on the backlog
Record the outcome, hand back the result, release the lease
Put a unit of work on the shared backlog for any qualified agent
Tombstone a key so a stale replica cannot resurrect it
Push status / plan / agentlog to the linked Google Doc
Read HUMAN directives (optional force poll)
Living-doc link + poll health (no secrets)
Give up an attempt: requeue it, dead-letter it, or cancel it
The roster: who is here, what they do, who is free
See which tasks are in flight and who holds them
The board: what exists, what is blocked, who holds what
Ask the backlog for work you can run — and take the lease in the same call
Messages still awaiting confirmation
Impose your own values when the automatic winner is wrong by intent
Read one key, or the whole shared document
Read the last N lines of the local markdown log
Catch up on peer activity without blocking
Hand a task back before its lease expires
Answer a question another agent asked you
Message every peer; queued and retried if they are offline
Replica id, content hash, peer count, negotiated protocol version per peer