Use Gryz MCP so an assistant can add a log entry, tick a task, fix one section, undo a bad change, or only suggest edits, without resending a whole document.

Before you start

A Gryz account (the free account includes MCP) with MCP connected. Follow Connect Gryz MCP in Cursor if you have not yet.
A document you want to keep current: a release tracker, a changelog, a decision log, a task list. Markdown works best because headings, tables, and checklists can be edited precisely.

A long tracker is awkward for an assistant to update if its only option is to resend the whole thing. That is slow, easy to get wrong, and risks overwriting someone else's change. Gryz lets an assistant read just an outline, add to the end, or change one section, and it keeps every earlier version so a mistake is one click to undo.

What the assistant can do

You say	What happens
"What is in my release tracker?"	It reads the outline: the headings and their sizes, not the text.
"Show me the Release 2.6 section."	It reads just that section.
"Add today's entry to the tracker."	It appends to the end. Everything already there stays exactly as it was.
"Add a row for the new task."	It adds a table row under the right heading, with the right number of columns.
"Tick off 'write docs'."	It ticks the checklist item and nothing else.
"Fix the typo in the intro."	It replaces that exact text, and only if it matches exactly once.
"What changed since yesterday?"	It reports which sections changed and who changed them.
"That last change was wrong, undo it."	It restores the earlier version as a new version.

Copy-paste prompt

Use my Gryz document "Release tracker" as the single place we record releases.
First read its outline. To add an update, append a new section under the
"Log" heading with today's date and two bullets. To mark work done, tick the
matching checklist item. Never resend the whole document. Tell me the new
version number when you are done. If the document has changed since you read
it, read it again and retry rather than overwriting.

Stay safe with more than one writer

You, a teammate, and several assistants can all work on one document. Assistants send the version they last read with every change. If the document has moved on, Gryz refuses the change instead of overwriting, and the assistant reads again and retries. For edits to different sections, the assistant can ask Gryz to combine them with the newer changes. If the same section changed, it tells you which one clashes.

Undo a bad change

Open the document in your dashboard and choose Edit. Version history lists every change with who made it, what they did, and when. Choose Show changes to see the difference, or Restore this version. Restoring never deletes anything, so you can undo it too. Each plan keeps a number of versions for a number of days; see version history and permissions.

Let assistants suggest instead of edit

Under the history panel, What assistants can do here has three settings:

Can edit: changes are made directly and saved in the history.
Suggestions only: assistants propose a change with a reason. You review the exact difference and accept or reject it.
Read only: assistants can read but not change anything.

Only you can accept a suggestion or change this setting. Assistants cannot approve their own suggestions.

Next steps

Exact inputs and error messages: MCP tools reference
Plan limits for history: Compare Gryz accounts and plans

Keep living docs current with your agent