Project & protocol
4 MCP tools. Each applies to the one project the server was launched with; every mutating call is one undo step and saves immediately.
backup_project
Writes a timestamped .ewbackup ZIP of the whole project into the user's backups folder (the same place the desktop app backs up to), keeping the 15 most recent. A safety snapshot to take before a risky batch of edits.
No parameters.
Example call
{
"name": "backup_project",
"arguments": {}
}
get_recent_changes
Lists what this session has changed so far, oldest first -- the honest transcript of the server's own edits.
No parameters.
Example call
{
"name": "get_recent_changes",
"arguments": {}
}
save_project
Saves the project to disk immediately. Every mutating tool already saves after its change; use this after undo_last or to be certain before handing back to the user.
No parameters.
Example call
{
"name": "save_project",
"arguments": {}
}
undo_last
Undoes the most recent change(s) made in this session and saves the project. Each mutating tool call is ONE undo step; the stack unwinds strictly last-in-first-out (there is no random-access undo of an earlier call -- use the desktop or re-edit for that). Pass "count" to undo several at once (default 1); it stops early, not erroring, if fewer changes remain. Fails honestly only when there is nothing to undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | no | How many of the most recent changes to undo (LIFO; default 1; stops early if fewer remain). |
Example call
{
"name": "undo_last",
"arguments": {
"count": 0
}
}