Maia Make Capabilities

Last modified: October 29, 2026

Introduction

Maia Make is a set of agentic development capabilities in Studio Pro that are available through a unified conversational interface. In one conversation, you can describe your requirements in natural language, and have Maia generate or modify any part of your app model, including domain models, pages, microflows, workflows, and translations. You can also ask Maia to explain existing documents, provide guidance, and integrate with external tools, such as Playwright and Figma, via MCP servers.

Maia Make also supports story-based development, allowing you to generate app artifacts based on existing user stories. As an agent that works directly with your app model, Maia determines which documents to create or change based on your goals, its built-in capabilities, and the MCP tools you enable. When necessary, it asks clarifying questions to gather more information.

Maia creates and modifies regular Mendix documents that you can review in the Studio Pro editors and undo as needed. That makes Maia Make useful throughout the application lifecycle, from generating a first version of an app to refactoring and extending an existing one. For more information, see Maia Across the Development Lifecycle.

For guidance on writing effective prompts for Maia, refer to Prompt Engineering.

Maia Make Capabilities Overview

Supported Document Types

Maia Make can generate new documents, modify existing documents, and explain app documents and structures through a unified conversational interface. The following table lists all document types that Maia Make can work with and the Studio Pro version in which support for each document type was introduced:

Document Type Available in Maia Make from Remarks
Domain model Studio Pro 11.8
Pages Studio Pro 11.8
Microflows Studio Pro 11.8 In Studio Pro 11.9 and above, Maia can delete flows and microflow objects, but cannot change activity types or replace complex configuration settings. In Studio Pro 11.8, Maia can change variable names, move objects, and reconnect flows for existing objects, but cannot delete objects or flows or change activity types.
Workflows Studio Pro 11.9
OQL Studio Pro 11.9
View entities Studio Pro 11.9
Enumerations Studio Pro 11.9
Constants Studio Pro 11.9
Modules Studio Pro 11.9
Java actions Studio Pro 11.9 In Studio Pro 11.9 and above, Java actions are read-only and cannot be generated. In Studio Pro 11.16 and above, Java action documents and source code files can be generated and edited.
JavaScript actions Studio Pro 11.9 Explain-only in Studio Pro 11.9. Generation, adding parameters, and updating the associated JavaScript file available from Studio Pro 11.10.
Navigation Studio Pro 11.11
Menu Studio Pro 11.11
Data Transformers Studio Pro 11.12
JSON Structures Studio Pro 11.13
Change Data Capture Studio Pro 11.14
Task Queues Studio Pro 11.15
Import Mappings Studio Pro 11.16 Maia can create import mappings with a JSON structure as the source and map them automatically to new entities. Changing existing import mappings is not supported.
Export Mappings Studio Pro 11.16 Maia can create export mappings with a JSON structure as the source and map them automatically to new entities. Changing existing export mappings is not supported.
External Database Connector Studio Pro 11.16

Maia Make Standalone Capabilities

The following table lists Maia Make Standalone Capabilities and the Studio Pro version in which each capability was introduced:

Capability Description Available in Maia Make from Remarks
Chat Answers questions about all aspects of Mendix development in the same chat in which you build. Studio Pro 11.8 Replaces Maia Chat, the earlier chat interface in Studio Pro.
Maia Explain Explains the purpose and logic of existing documents. Studio Pro 11.8 Can be used directly in the chat interface, or in the App Explorer by right-clicking a document and clicking Maia Explain.
Maia MCP Client Connects Maia to external MCP servers, giving it access to third-party tools. Studio Pro 11.8
Studio Pro MCP Server Exposes Studio Pro as an MCP server for use by external AI tools. Studio Pro 11.10
Maia Web Fetch Fetches and reads content from public websites and APIs. Studio Pro 11.10
Maia Agent Skills (SKILLS.md) Extends Maia with reusable knowledge. Studio Pro 11.11 Maia can create and edit skills directly in chat, for both project-level and module-level skills, from Studio Pro 11.15.
Maia Agent Instructions (AGENTS.md) Extends Maia with instructions to be followed with every prompt Studio Pro 11.12
Maia Plan Mode Allows Maia to maintain implementation plans. Studio Pro 11.16

Maia Make General Capabilities

The following table lists the general capabilities of Maia Make and the Studio Pro version in which support for each capability was introduced:

Capability Description Available in Maia Make from Remarks
Story-based development Generates app artifacts based on existing user stories to support story-driven development workflows. Studio Pro 11.8
Attach files Allows you to provide PDFs and images as input to help Maia better understand your requirements. Studio Pro 11.8 In Studio Pro 11.12 and above, you can attach Markdown files. In Studio Pro 11.16 and above, you can attach CSV, JSON, XML, YAML, and HTML files. Attached files are available to Maia for the rest of the session.
Adding documents as context Lets you add relevant documents to provide Maia with additional context. Studio Pro 11.8
Editing existing documents Enables Maia to modify existing documents, including renaming elements. Studio Pro 11.8
Removing elements Allows Maia to remove elements from documents to support more advanced refactoring tasks. Studio Pro 11.9
Undo support Allows you to undo Maia-generated changes on a per-document basis. Studio Pro 11.9
Folder structure support Organizes new documents into existing folders and follows your established folder hierarchy when generating content. Studio Pro 11.10 Not supported for pages.
Themes and styling Allows Maia to modify theme variables, create custom styling, and manage design properties. Studio Pro 11.12
Explain and solve consistency errors Allows you to use Maia to explain or solve problems by right-clicking the item in the Errors pane. Studio Pro 11.12.1
Translations Allows Maia to create and update translations in your app. Studio Pro 11.15
Delete documents Allows Maia to delete documents in your app. Studio Pro 11.16
UI testing Allows Maia to test the running app in the browser. Studio Pro 11.16 Testing needs to be done in Edge or Chrome.

Using Maia Make Capabilities

Maia Make capabilities are enabled by default. You can disable them in Studio Pro Preferences, via the Maia tab.

To access the conversational interface and Maia Make capabilities, in the upper-right corner of Studio Pro, click the Maia pane. It appears under the Chat tab:

Maia Make interface

Alternatively, you can click View on the Studio Pro top bar and select Maia to open the interface.

Maia Make Capabilities Interface Overview

The conversational interface includes the following features.

New Chat

Clicking New Chat allows you to clear the messages and start a new conversation that does not reference your current chat.

Settings

The Settings option ( ) allows you to manage your MCP Servers, agent skills, and export your Maia agent session. It also allows you to view and manage your tool permissions. You can configure permissions to Always Allow or allow only in the current session.

Configure MCP Connections (Studio Pro 11.14 and below)

This option ( ) allows you to connect external MCP servers to Maia, giving it access to third-party tools during chat. For more information on how to configure MCP connections, see Maia MCP Client.

Add

Add allows you to attach images, PDFs, or user stories to help Maia understand your requirements better.

Add File to Maia Chat

The Add file to Maia Chat option (@ icon) allows you to add certain logic or pages to Maia as context. You can also access this option by right-clicking the documents (microflows or pages) in the App Explorer, where it appears in the context menu.

Skills

The Skills option opens the Skills tab of the Maia Settings pane and gives you a full overview of the agent skills in your app. This button only appears when you add an agent skill to your app.

Changed List

A list of items added or changed by Maia appears above the chat box. Click an entry to open the relevant document. To undo all changes, click Undo all. To undo a single change, click the undo button on the right side of that item.

Clarifying Questions

When Maia needs more information, it asks clarifying questions through a dedicated UI to improve the quality of its response.

Reviewing and Controlling Maia Changes

Maia changes regular documents in your app. You stay in control of these changes in the following ways:

  • Changed list – After each request, the Changed List shows the documents that Maia added or changed. Select an entry to open the document in its editor.
  • Consistency checks – Studio Pro checks the documents that Maia creates or changes for consistency errors. In Studio Pro 11.12.1 and above, you can right-click an item in the Errors pane to ask Maia to explain or solve it.
  • Undo – In Studio Pro 11.9 and above, you can undo Maia changes per document or for all documents.
  • Version control – Maia changes are part of your local changes, so you decide when to commit them. For more information, see Version Control.
  • Settings – You can disable Maia Make capabilities in Studio Pro Preferences on the AI tab.

For practices that help you review and control AI-generated changes, see the Working Practices for Agentic Development section of Agentic and Model-Driven Development.

Save a Maia Session

A Maia session contains your conversation history and context, which can help analyze Maia's responses and behavior for troubleshooting or support purposes. To save a Maia session, go to Help > Support Tools > Capture Maia Agent Session.

In Studio Pro 11.9 - 11.11, this option is found at Help > Support Tools > Dump Maia Agent Session.

Configuring a Custom AI Provider

By default, Maia uses the Mendix platform's AI service. You can configure Maia to use your own LLM provider instead (also known as bring your own LLM or BYO LLM).

To enable custom LLM provider configuration, follow these steps:

  1. Open the Studio Pro settings.
  2. In the Preferences dialog box that opens, go to the New Features tab.
  3. Select the Enable configuring a custom AI provider for Maia checkbox, then click OK.

After enabling this feature, a Settings ( ) icon appears in the upper-right corner of the Maia pane.

Provider Configuration

Custom AI provider settings are per-project and local to your workstation. Each app can have its own configuration, and settings are not committed to version control.

Mendix Platform

The Mendix platform AI service is the default, recommended option and requires no configuration. Some Mendix platform optimizations may not be available if you use a custom LLM provider instead.

Amazon Bedrock

To configure Amazon Bedrock as your LLM provider, follow these steps:

  1. Click Settings ( ) in the Maia pane.
  2. Select Amazon Bedrock from the LLM Provider list.
  3. Create an API key in AWS, then enter the Base URL and your API Key. Studio Pro stores the API key securely across sessions.
  4. Enter the Model ID. You can find available model IDs in your AWS Bedrock console.
  5. Click Save Config.

OpenAI Compatible

To configure an OpenAI-compatible provider, follow these steps:

  1. Click Settings ( ) in the Maia pane.
  2. Select OpenAI Compatible from the LLM Provider list.
  3. Enter the Base URL for your API endpoint.
  4. Enter the Model ID.
  5. Optional: Enter your API Key. Studio Pro stores this key securely across sessions.
  6. Click Save Config.

LLM Gateway Configuration for Private Mendix Platform

Private Mendix Platform provides an environment where you can develop and deploy your applications within your own enterprise security boundary to ensure the highest levels of data security and compliance. Because Private Mendix Platform instances are hosted within the enterprise firewall, selecting an LLM provider other than the default Mendix Platform requires you to also configure the LLM Gateway URL.

The LLM Gateway URL is configured during the installation or upgrade of Private Mendix Platform. For more information, see Installing Maia for Private Mendix Platform.

Best Practices

Text Input

To achieve optimal results, provide context about your app or the document you are working on by describing its main use cases, customer needs, or other relevant details. The more Maia knows about what you are building, the more tailored and accurate the generated results will be.

Providing Context

Below are some examples of prompts you can use as a starting point:

  • The app will help users...
  • This module handles...
  • Customers need to be able to...
  • The page will be used to...
  • Generate a workflow for a process that...
  • This feature allows users to...

Editing and Improving

Below are examples of prompts you can use to ask Maia to make further edits or request explanations and suggestions for improving a document:

  • Can you explain the function and purpose of this document?
  • I want an area on the page where users can...
  • Remove the ... widget.
  • How can I make this page more user-friendly or visually appealing?
  • Could you identify any potential issues with this document and recommend solutions?
  • Can you give me suggestions to improve this workflow?

Image Input

The image size is limited to 512 KB. Make sure to select a clear image to help Maia better understand your request. For example, you can provide a screenshot, a photo, a design mock-up, or a close-up picture of a drawing. Avoid heavily compressed or low-quality images, as these may result in the loss of important details.

Keep in mind that Maia analyzes only the structure of the image. Maia does not change the theming of your app, such as the color scheme. This can cause some differences between the provided image and the generated page.

Microflows

When generating microflows, consider the following additional guidelines:

  • Be specific: Clearly describe the desired outcome and the steps involved. For example, instead of using Create a user, use Create a new user object, set its name attribute to 'John Doe', and commit it.
  • Use keywords: Incorporate terms relevant to microflow activities, such as create object, retrieve, change object, show message, loop, or decision. This can help with correct microflow generation.
  • Provide context: If your microflow interacts with existing entities or attributes, mention them in your text input.

Workflows

You can provide a BPMN image representing employee onboarding alongside your text input. Maia can analyze the image, rework it using Mendix Workflows terminology, and generate the corresponding activities. Use text input alongside the image to specify any differences. For example, "Generate a workflow based on this BPMN image, but make sure it waits before sending an email to the new employee."

Read More