Some ideas for the MCP

Not possible through the MCP (Studio Pro UI or computer use needed)

• Snippets: Pages$Snippet is not reachable with the ped_* or pg_* tools (ped_find_document rejects the type), so any widget, class or design property change inside a snippet is done by hand in Studio Pro.
• Deleting documents: a whole page, microflow, Java action or other document cannot be deleted; this is done with a right-click Delete in App Explorer.
• Association delete behaviour: setting “on delete of X, delete Y as well” is refused as element-valued.
• Module security: Security$ModuleSecurity is not reachable, so module roles, entity access rules, page and microflow access, and mapping module roles to user roles are all Studio Pro dialog work.
• Marketplace and read-only modules: pg_patch_page refuses edits in Encryption, OIDC, Email_Connector and similar modules (even a layout swap).
• Moving documents into folders: new pages land at the module root, and moving them into a folder needs a drag and drop in App Explorer.
• Save All: ped_update_document leaves documents dirty in Studio Pro, and pg_patch_page on an already open page only reaches disk after Ctrl+Shift+S.
• Git operations: committing, merging, aborting a merge and reverting all happen in Studio Pro’s version control UI.
• Synchronize App Directory (F4): needed after a change to design-properties.json before core widgets stop reporting “design property not supported”.
• Running or rebuilding the app: model changes only show after you re-run locally; theme SCSS is the exception (hot-reloaded).

Possible, but only with a workaround

• Error handler flows: the SequenceFlow constructor ignores isErrorHandler, so it needs a second ped_update_document after the flow is created.
• String length and localizeDate: not taken at entity creation and have to be patched afterwards on /type/length and /type/localizeDate.
• Page roles: pages created by pg_patch_page have no allowed roles, and the error only appears once a button references the page, so roles are added separately on /allowedRoles.
• Moving microflow objects: setting /x alone on a position is refused, so the whole relativeMiddlePoint object has to be replaced.
• Inserting into an existing microflow: removing the old flow and adding the new flows have to be separate calls, with objects referenced by index.
• Loops and splits: iterator and output variable names must be unique across loops in one microflow, and chained exclusive splits need an explicit “false” case on the flow to the next split.
• Page JSON: every appearance needs "$Type":"Pages$Appearance" or creation fails with a missing Type error.
• ped_write_document: has dropped the Studio Pro connection, so SCSS and other theme files are safer to edit directly on disk.
• Finding things: reading by path needs array indices up front, and there is no usage search, so locating a document or its references is done by grepping the .mxunit files in mprcontents.
• Target checkout

Lead, don't follow ;)