context_update
Update a node — rename, set status, stamp a version, clear metadata with null
How to use it
context_update is exposed by the ContextNest MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the context_update tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install ContextNest
docker run -i --rm contextnest-mcp # demo vault baked into the imageOther tools in ContextNest (34)
Apply a suggestion: patch, bump version, write new canonical bytes, archive
Create a node — own id, publish: false, initial status, note, full skill block
Delete a node and its history; returns the deleted node's title
Read one node (includeraw, verifychecksum, allowrejected)
Bulk create-and-publish from documents and/or existing ids — one checkpoint for the batch
Open a vault: instructions, configuration, path, and what it holds (includenodes to also list nodes)
List nodes with type / status / tag filters (includeretired, full, limit)
List every nest in the central registry
List packs with their includes and excludes
Publish a node; takes a note, returns the chainhash
Selector query with graph traversal (includedrafts)
Reconstruct a specific version
Resolve a selector to full bodies within a token budget
Full-text search with graph traversal
Verify every hash chain in the vault
List a document's version history
contextcreate
contextdelete
Get the document format spec (call before creating docs)
List recent checkpoints
contextlist
List all staged suggestions for a document
contextpublish
contextget
Return the context.yaml index
Resolve and return a context pack with documents
contextreconstruct
Reject a suggestion: archive with required reason, emit a chain event
contextresolve
contextsearch
Capture a drifted live file as a staged suggestion under suggestions/
contextupdate
contextinit
contextverify