New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Live Edit With Studio Pro

by mendixlabs in mendixlabs/mxcli

Change the model through mxcli while Studio Pro has the project open, with edits appearing live over MCP.

Apache-2.0Auto-check passedAgent Workflows

Install Live Edit With Studio Pro

skills CLI
$ npx skills add mendixlabs/mxcli --skill live-edit-with-studio-pro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mendixlabs/mxcli live-edit-with-studio-pro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/live-edit-with-studio-pro .claude/skills/live-edit-with-studio-pro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
live-edit-with-studio-pro
GitHub stars
128
Token cost
~1.2k tokens
SKILL.md length
659 words
Files
1
Skills in repo
72
Repo updated
First seen
Licence
Apache-2.0

At a glance

Change the model through mxcli while Studio Pro has the project open, with edits appearing live over MCP.

  • Claude Code and Studio Pro run on the same machine and a save-and-reopen cycle is unwanted
  • SKILL.md covers When to use this skill, How it works (hybrid: local…, Connect and What you can change via MCP —…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve MCP servers

What it does

Live Edit With Studio Pro is an agent 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.

When your agent uses it

  • Claude Code and Studio Pro run on the same machine and a save-and-reopen cycle is unwanted
  • Tasks that involve MCP servers

Example prompts

  • “/live-edit-with-studio-pro”

What it can do on your machine

Read from SKILL.md and the folder at commit 20a6c89. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Live Edit With Studio Pro loads about 1.2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mendixlabs/mxcli at commit 20a6c89, republished under its Apache-2.0 licence (© mendixlabs). 659 words, ~1,243 tokens.

Download SKILL.mdSave it as .claude/skills/live-edit-with-studio-pro/SKILL.md (or your agent's skills folder).
name
live-edit-with-studio-pro
description
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.

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
mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 \
      -p /path/to/app.mpr \
      -c "create entity MyModule.Customer"

--mcp-dial localhost:7782 keeps the Host header localhost while dialing the port. (Plain --mcp http://localhost:7782/mcp may also work if your Studio Pro accepts a port-suffixed Host — try it; fall back to the --mcp-dial form if it is rejected.)

Run a script the same way: mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 -p app.mpr exec changes.mdl.

What you can change via MCP — check first

What's authorable over MCP depends on the Studio Pro version and on this session. The capability surface changes per release, but it also depends on your Studio Pro preferences (some tools are togglable) and on which MCP servers you have connected to Studio Pro. So the answer is not derivable from a version number — ask the connected server, every session, before generating MDL:

bash
mxcli mcp capabilities -p /path/to/app.mpr --mcp http://localhost/mcp --mcp-dial localhost:7782

It prints, for this session: what's authorable (modules, entities + ALTER, associations, enumerations, constants, microflows, pages + ALTER PAGE, workflows, navigation, entity access rules, documents into folders), what's not (e.g. nanoflows, Java actions, business-event services, view entities, security roles, MOVE/re-parent, attribute type change), and the live tool list. Treat anything reported as not authorable as off-limits over MCP — do it in Studio Pro or against the on-disk .mpr instead.

A feature can also be reported unavailable because this session lacks a tool it needs, or because the tool probe did not answer; the report says which, and mxcli fails closed rather than assuming a tool is there. Quote the whole report in a bug report — a Studio Pro version number alone does not identify the surface you had.

New modules and their dependents resolve within the same run, so create module X; create enumeration X.Status (...) works in one script. Place a document in a folder at create time (create microflow X.MF folder 'A/B'), since MOVE can't re-parent over MCP.

Show full SKILL.md (185 more words)Show less

Two MCP servers — use the built-in one by default

The machine may run two MCP servers:

  • Studio Pro built-in (port 7782 by default) — model authoring. Use this by default. From 11.13 Studio Pro auto-selects a free port when 7782 is taken, so multiple instances can run side by side. The active port is shown in Studio Pro's status bar (and set under Preferences > AI > MCP Server) — read it there rather than assuming 7782, and pass it to --mcp-dial.
  • Concord (port 7783) — a temporary gap-filler with operational/refactor tools (delete_document, save_all, run_app, check_model). Only reach for Concord when the built-in server lacks the capability you need.

Caveats

  • Writes are unsaved. They land in Studio Pro's in-memory model (shown as unsaved). Save in Studio Pro to persist to disk.
  • No DROP of standalone documents (enumeration / microflow / page) through the built-in server — it has no delete tool. Remove them in Studio Pro (or via Concord's delete_document).
  • -p must match the open project. A mismatched -p silently reads the wrong model.

Verify your change

Read it back through the same connection (in-session edits are visible), or look in Studio Pro:

bash
mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 -p app.mpr -c "list entities in MyModule"

© mendixlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/mendix/live-edit-with-studio-pro of mendixlabs/mxcli.

Open the folder on GitHubat commit 20a6c89

Compare with similar skills

Live Edit With Studio Pro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Live Edit With Studio Pro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Live Edit With Studio Pro this skillmendixlabs/mxcli128—~1.2kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from mendixlabs/mxcli

All 72 skills in this repo

  • Mendix Odata Pushdown

    mendixlabs/mxcli

    Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…

    128 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Mendix Vega Charts

    mendixlabs/mxcli

    Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.

    128 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Agents

    mendixlabs/mxcli

    Author Mendix AI agent documents in MDL — Model, Knowledge Base, Consumed MCP Service and Agent, with variables, tools and multi-line prompts.

    128 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

  • Mendix Bulk Oql Dml

    mendixlabs/mxcli

    Run set-based INSERT, UPDATE and DELETE against Mendix entities through OQL statements, which the runtime supports and Studio Pro cannot author.

    128 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Business Events

    mendixlabs/mxcli

    Define event-driven APIs over Kafka with Mendix business event services — publish and subscribe contracts, CREATE/DROP/DESCRIBE.

    128 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Catalog Search

    mendixlabs/mxcli

    Search the Mendix Catalog platform service registry (catalog.mendix.com) from the CLI to find services published across an organisation.

    128 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Works with

Categories

Questions about Live Edit With Studio Pro

What does Live Edit With Studio Pro do?

Change the model through mxcli while Studio Pro has the project open, with edits appearing live over MCP. Live Edit With Studio Pro is an agent skill from mendixlabs/mxcli. Change the model through mxcli while Studio Pro has the project open, with edits appearing live over MCP.

When should I use Live Edit With Studio Pro?

Live Edit With Studio Pro fits situations like: Claude Code and Studio Pro run on the same machine and a save-and-reopen cycle is unwanted; tasks that involve MCP servers.

How do I install Live Edit With Studio Pro in Claude Code?

Run `npx skills add mendixlabs/mxcli --skill live-edit-with-studio-pro -a claude-code`. Or copy the skill folder (.claude/skills/mendix/live-edit-with-studio-pro in mendixlabs/mxcli) into .claude/skills/live-edit-with-studio-pro in your project. Claude Code loads it when a task matches its description.

How do I install Live Edit With Studio Pro in Codex?

Run `npx skills add mendixlabs/mxcli --skill live-edit-with-studio-pro -a codex`. Or copy the skill folder (.claude/skills/mendix/live-edit-with-studio-pro in mendixlabs/mxcli) into .agents/skills/live-edit-with-studio-pro in your project. Codex loads it when a task matches its description.

Can I use Live Edit With Studio Pro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill live-edit-with-studio-pro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/live-edit-with-studio-pro, .gemini/skills/live-edit-with-studio-pro, .github/skills/live-edit-with-studio-pro and .opencode/skills/live-edit-with-studio-pro in your project.

What does Live Edit With Studio Pro need to run?

SKILL.md names no scripts, command-line tools or credentials: Live Edit With Studio Pro is instructions for the agent only.

Does Live Edit With Studio Pro access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Live Edit With Studio Pro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Live Edit With Studio Pro use?

Live Edit With Studio Pro is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Live Edit With Studio Pro use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Live Edit With Studio Pro?

Skills that share tags, products or a category with Live Edit With Studio Pro: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Live Edit With Studio Pro?

mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 72 skills in this directory. The repository was last updated on October 7, 2026.

Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.