Cluade in Mendix 11 works very nicely.

The only real limts are it can't edit snippets or update security, other than that, it does a very nice job of finding and fixing issues. after a bit of use it is creating very nice workflows with lots of error checking.

Visually the workflow is a mess, Mia is much better in this regard, but the code works and in most cases does what you want.

Some of its insights have made a big difference in the app.

I use Fable and pay the $100 a month fee. On a busy week I can get close to using everything, but I often will use Opus to do the low-level work and swith to Fable for the more complex areas.

For a principal in a small business, I have found this to be a powerful addition to creating apps that help the business.

I used Claude to guid me through how to setup in Mendix, not hard, but there is a little bit of configuration required. I am on a mac running parallels.

for 9.7 you can use mendix cli(mxcli) and claude or any other AI tools which is available with you.

For mendix 11, maia make is giving promising results but you need to be very clear about your requirement or even after it is changed also, you can rework on the microflows individually. It is better to work with individual stories than a complete project.

Below I have posted the setup, however all I did to get things working was launch Mendix 11.3, launch Cluade desktop and then asked, "How do I setup Claude to work with Mendix 11.3", it it went through process.

Here is my notes from when I did it.

Here's the setup I've been running for the last couple of months (Claude Code + Studio Pro). It's been a genuine step change for how I build.

**The short version:** Studio Pro 11.10+ ships a native MCP server (GA since June 2026). You enable it in preferences, register it with Claude Code with one command, and Claude can then read and edit your app model directly — microflows, domain model, pages — with every change appearing in Studio Pro in real time.

**Setup**

1. Upgrade to Studio Pro 11.10 or later, and make sure you're signed in — the MCP server requires sign-in and an internet connection.

2. In Studio Pro, go to **Edit → Preferences → AI → MCP Server** and check **Enable MCP Server**. Note the port (configurable in the same panel).

3. Install Claude Code (https://claude.com/claude-code), then register the server from a terminal:

`claude mcp add mendix --scope user --transport http http://localhost:7782/mcp`

Use whatever port you set in preferences. `--scope user` registers it once for every project folder instead of just the current one.

4. Open your app in Studio Pro, start Claude Code, and ask for something — it discovers the Mendix tools automatically.

**What Claude can do with it**

Essentially Maia feature parity: read, create, and edit microflows, domain models, pages, and enumerations; create modules; run the model error check; install Marketplace modules; read and write project files; and search the official Mendix docs. Edits land in the model as they happen, so you review in Studio Pro in real time.

**Practical things I learned along the way**

- The MCP server only exists while Studio Pro is open with your app loaded, and it operates on whichever app is open (one at a time).

- Nanoflows aren't visible through the MCP server. Workaround: have Claude read the compiled JS under `deployment/web/nanoflows/`.

- Page XPath data sources evaluate against the database — a page over uncommitted objects needs a microflow data source instead. Classic trap when Claude builds pages.

- When Claude inserts several activities into a flow in one operation, they can land in reverse order. Have it re-read the flow after wiring, and always review in Studio Pro — a clean error check is not proof the wiring is right.

- The 11.10 docs list page *generation* as not supported over MCP yet; page *editing* has worked fine for me.

- Claude edits the model, but you still run locally from Studio Pro to test.

- Give Claude a CLAUDE.md file describing your naming conventions and module layout — the quality compounds fast.

- Tokens are billed through your own Claude account, not Mendix.

Official docs: https://docs.mendix.com/refguide/studio-pro-mcp-server/

Happy to answer questions — I've been using this daily on a real production app.

What might not be clear, I do not use Mia inside of mendix, or at least rarely. I use the Claude desktop app and generate prompts there.

I tend to do smaller features and bug fixes in small groups and I watch my context window in Claude and keep it under 500k

I recently needed to import some complex data into multiple entitiys, it did an excellent job of createing all the parts needed. Entitys, pages, forms, and workflows with safety checks on each variable. While none of this is hard, when you have 200 fields to import, it can be time consuming.

It was not 100% perfect, but easily 95% perfect and the few issues I had were mostly because I didn't explain things well enough.

My workflow has been to create a roadmap of everything that I want done and I spend a lot of time explaining what I want and having Cluade explain what it is going to do. This takes time, but pays off when you start creating code.

My next big project is converting a large app from Mendix 10 to Mendix 11 (dogo to react). This has about 465 data grid's that need to convert to Data Grid 2. I am picking about how I want the grid to look and I think I am at a point that Cluade will be able to redo each grid in the style I want. I will probably go over my limits, but well worth a few hundered dollars to automate the process.

Martin