live-edit-with-studio-pro skillA
live-edit-with-studio-pro is agent-read markdown (skill) from mendixlabs/mxcli: Change the model through mxcli while Studio Pro has the project open, with edits appearing live over MCP. Use when Claude Code and Studio Pro run on the same machine and a save-and-reopen cycle is unwanted..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Live-Editing an Open Studio Pro Project with mxcli (MCP) Use mxcli to change the model **while Studio Pro has the project open**, with edits appearing live in Studio Pro — no save-and-reopen cycle. This is the workflow when Claude Code runs on the same machine as Studio Pro (e.g. an in-IDE terminal). ## When to use this skill - Studio Pro is open on the project and you want mxcli changes to show up live. - mxcli and Studio Pro run on the **same machine** (same `localhost`). If Studio Pro is **not** open, use the normal file-based flow instead (`mxcli -p app.mpr -c "..."` with no `--mcp`), which edits the `.mpr` on disk. ## How it works (hybrid: local reads, live writes) - **Reads** come from the local `.mpr` you pass with `-p`. - **Writes** go to Studio Pro's live, in-memory model via its built-in MCP server. - Therefore **`-p` MUST be the exact project Studio Pro currently has open**, or reads and writes will describe different projects. ## Connect Studio Pro's MCP server listens on `localhost:7782` and requires the HTTP `Host` header to be `localhost` (a DNS-rebinding guard). Same-machine, **no port-forwarding/socat is needed**: ```bash …
Read the whole file at its exact version.
How to install
mdr add mendixlabs/mxcli/live-edit-with-studio-pro@git:20260821.ff81a24mdr add mendixlabs/mxcli/live-edit-with-studio-pro@sha256:9b9e757119e48482Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_a45fknphuhaapbbu)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4991 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mendixlabs/mxcli · 124 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a45fknphuhaapbbu GET https://markdownregistry.com/api/v1/resolve?ref=mendixlabs/mxcli/live-edit-with-studio-pro GET https://markdownregistry.com/api/v1/blob/9b9e757119e4848246c7a293f5c34b2e7b19770998eb5950067f9f8f8b2f707f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.