From d9568b4e9a14ba22d704d4a0519996ca7a6cd123 Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Mon, 26 Oct 2026 08:27:32 +0100 Subject: [PATCH 1/3] Maia Spec --- .../developerportal/maia-plan/create-app/define-scope.md | 6 +++--- .../developerportal/maia-plan/create-app/generate-plan.md | 6 +++--- .../developerportal/maia-plan/create-app/project-context.md | 4 +++- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md index 56c3b2528af..fb60b405825 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md +++ b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md @@ -9,7 +9,7 @@ weight: 20 Work with Maia to refine and detail the project scope, including the goal, success criteria, target users, and requirements. -1. After you click **Generate Plan**, the **Define Scope** window appears, and Maia starts populating it with the proposed project scope. +1. After you click **Create Plan**, the **Define Scope** window appears, and Maia starts populating it with the proposed project scope. The app plan becomes available on the **Projects** page as soon as you click **Generate Plan** at the beginning of the workflow. You can return to the plan at any time after you leave it, and you can add team members to the app. After the **Define Scope** window is populated, you can see the following information generated by Maia: @@ -38,5 +38,5 @@ Work with Maia to refine and detail the project scope, including the goal, succe You can use the pane on the right to chat with Maia about your requirements for the new app. -2. After you review the project scope and make any necessary changes, click **Approve & Generate**. - You can also click **Save and Exit** to save all the changes and leave the flow. +2. After you review the project scope and make any necessary changes, click **Approve to Create Specs**. This prompts Maia to start turning your input into a detailed set of specs, with each spec mapping to each distinct capability. + You can also click **Save** to save all the changes and leave the flow. diff --git a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md index 782476ac95a..37a635fd4c8 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md +++ b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md @@ -7,10 +7,10 @@ weight: 30 ## Introduction -Maia translates your defined scope into a concrete plan, which includes a series of epics and stories. +Maia translates your defined scope into a concrete set of specs, where each spec corresponds to a specific capability. -1. After you click **Approve & Generate**, the **Generate Plan** window appears, and Maia starts populating it with the proposed plan based on the project scope. - After the **Generate Plan** window is populated, you can see the following information generated by Maia: +1. After you click **Approve to Create Specs**, the **Spec** window appears, and Maia starts populating it with the proposed plan based on the project scope. + After the **Spec** window is populated, you can see the following information generated by Maia: * Cards for each epic that contributes to building the app. You can remove epics by hovering over them, then clicking the trash can icon. diff --git a/content/en/docs/developerportal/maia-plan/create-app/project-context.md b/content/en/docs/developerportal/maia-plan/create-app/project-context.md index e716fac6475..b3444ce1cbe 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/project-context.md +++ b/content/en/docs/developerportal/maia-plan/create-app/project-context.md @@ -27,4 +27,6 @@ Providing context is the foundation for Maia to build your project plan. Give Ma * **Use the latest version** * **Use a starter app with a predefined Studio Pro version** -5. Click **Generate Plan**. +5. Click **Create Plan**. + +Maia analyzes the context in the background, and starts producing a scope. From 12cb75c61e5ca6b1cc6681606e582663ce5dd256 Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Tue, 27 Oct 2026 16:24:05 +0100 Subject: [PATCH 2/3] Updates per design changes --- .../maia-plan/create-app/define-scope.md | 2 +- .../maia-plan/create-app/generate-plan.md | 20 +++++-------------- 2 files changed, 6 insertions(+), 16 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md index fb60b405825..4de9e2701df 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md +++ b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md @@ -38,5 +38,5 @@ Work with Maia to refine and detail the project scope, including the goal, succe You can use the pane on the right to chat with Maia about your requirements for the new app. -2. After you review the project scope and make any necessary changes, click **Approve to Create Specs**. This prompts Maia to start turning your input into a detailed set of specs, with each spec mapping to each distinct capability. +2. After you review the project scope and make any necessary changes, click **Create Specs**. This prompts Maia to start turning your input into a detailed set of specs, with each spec mapping to each distinct capability. You can also click **Save** to save all the changes and leave the flow. diff --git a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md index 37a635fd4c8..aeae7dd2daf 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md +++ b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md @@ -9,27 +9,17 @@ weight: 30 Maia translates your defined scope into a concrete set of specs, where each spec corresponds to a specific capability. -1. After you click **Approve to Create Specs**, the **Spec** window appears, and Maia starts populating it with the proposed plan based on the project scope. - After the **Spec** window is populated, you can see the following information generated by Maia: - - * Cards for each epic that contributes to building the app. - You can remove epics by hovering over them, then clicking the trash can icon. - Click the card to: - - * See the list of stories for an epic in the right side panel. - * Edit the description or details of the epic. - - You can perform the following actions on each story: - - * To see the full details of a story or edit it, click the three-dot menu, then select **Edit**. - * To remove a story, click the three-dot menu, then select **Delete**. +1. After you click **Create Specs**, the **Spec** window appears, and Maia starts populating it with the proposed specs based on the project scope. The generated specs are listed in the left-hand pane. Each spec is made up of several requirements. For project management purposes, a spec corresponds to an epic, and a requirement corresponds to a story. 2. While the project plan is being generated, you have these options: * **Previous** – Click this button to return to the **Define Scope** window. Any changes you have made are saved. * **Save and Exit** – Save all the changes and leave the flow. - After the project plan is fully generated and you have made any necessary changes, click **Start Building**. + After the project plan is fully generated and you have made any necessary changes, click one of the available options: + + * **Open in Jira** – Start managing the project in Jira. + * **Build in Maia Make** – Open the project in Studio Pro's Maia Make. ### Recommended Marketplace Components {#recommender} From d51be30218be84f6842cc75d464745f6c4cbdfac Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Fri, 30 Oct 2026 16:33:41 +0100 Subject: [PATCH 3/3] Changed app name + URLs & redirects --- .../control-center/maia/maia-resources.md | 2 +- content/en/docs/developerportal/_index.md | 2 +- .../docs/developerportal/maia-plan/_index.md | 10 +++-- .../maia-plan/create-app/_index.md | 18 +++++---- .../maia-plan/create-app/define-scope.md | 6 ++- .../maia-plan/create-app/generate-plan.md | 6 ++- .../maia-plan/create-app/project-context.md | 6 ++- .../maia-plan/create-app/start-development.md | 36 +++++++++--------- .../maia-plan/create-app/starter-app.md | 14 ++++--- .../maia-plan/maia-plan-mcp/_index.md | 38 +++++++++---------- .../maia-plan-mcp/troubleshooting.md | 6 +-- content/en/docs/mendix-portal/maia-portal.md | 6 +-- .../refguide/mendix-ai-assistance/_index.md | 6 +-- .../agentic-development.md | 2 +- .../maia-development-lifecycle.md | 6 +-- .../maia-external-agents.md | 10 ++--- .../maia-make/studio-pro-mcp-server.md | 4 +- .../releasenotes/developer-portal/2026.md | 18 ++++----- .../feature-release-calendar/_index.md | 4 +- 19 files changed, 107 insertions(+), 93 deletions(-) diff --git a/content/en/docs/control-center/maia/maia-resources.md b/content/en/docs/control-center/maia/maia-resources.md index 01c6bccd6df..b1415c8409c 100644 --- a/content/en/docs/control-center/maia/maia-resources.md +++ b/content/en/docs/control-center/maia/maia-resources.md @@ -10,7 +10,7 @@ weight: 20 The Maia **Resources** page allows you to increase the capacity of Maia Units for using Maia Make in Studio Pro. From here, you can provision, upgrade, downgrade, and deprovision Maia Units and manage the resources for Maia Make for your company. For more information on Maia Make’s capabilities, see [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/). {{% alert color="info" %}} -Maia Units are only required for Maia Make. Other Maia features (for example, Maia Plan) do not require Maia Units. +Maia Units are only required for Maia Make. Other Maia features (for example, Maia Spec) do not require Maia Units. {{% /alert %}} ## Prerequisites diff --git a/content/en/docs/developerportal/_index.md b/content/en/docs/developerportal/_index.md index ffcada53291..3434217e0f4 100644 --- a/content/en/docs/developerportal/_index.md +++ b/content/en/docs/developerportal/_index.md @@ -29,7 +29,7 @@ The following sections describe the process for each option. ### Creating an App with Maia -Follow the steps in [Maia Plan](/developerportal/maia-plan/) to enlist Maia's help in planning and creating an app. +Follow the steps in [Maia Spec](/developerportal/maia-spec/) to enlist Maia's help in planning and creating an app. ### Creating an App from a Starter App Template diff --git a/content/en/docs/developerportal/maia-plan/_index.md b/content/en/docs/developerportal/maia-plan/_index.md index fd8eee84f6f..bf2da4b9763 100644 --- a/content/en/docs/developerportal/maia-plan/_index.md +++ b/content/en/docs/developerportal/maia-plan/_index.md @@ -1,18 +1,20 @@ --- -title: "Maia Plan" -url: /developerportal/maia-plan/ +title: "Maia Spec" +url: /developerportal/maia-spec/ description: "Describes the process of planning and building an app using Maia." weight: 1 no_list: false description_list: true +aliases: + - /developerportal/maia-plan/ --- ## Introduction -Maia Plan helps you create a detailed project plan, based on which you can then generate your app with [Maia Make](/refguide/maia-make/). The pages in this category describe how to provide project context, review and refine the generated project scope, and approve the solution proposal to start app development. +Maia Spec helps you create a detailed project plan, based on which you can then generate your app with [Maia Make](/refguide/maia-make/). The pages in this category describe how to provide project context, review and refine the generated project scope, and approve the solution proposal to start app development. {{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia entry point" max-width=50% >}} -Maia Plan covers the planning stage of the application lifecycle. You can use the stories from the plan as input when building your app in Studio Pro with Maia Make, or have external AI agents read the plan through [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/). +Maia Spec covers the planning stage of the application lifecycle. You can use the stories from the plan as input when building your app in Studio Pro with Maia Make, or have external AI agents read the plan through [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/). For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/). ## Documents in This Category diff --git a/content/en/docs/developerportal/maia-plan/create-app/_index.md b/content/en/docs/developerportal/maia-plan/create-app/_index.md index 0dc565f3e4f..3ba3936a324 100755 --- a/content/en/docs/developerportal/maia-plan/create-app/_index.md +++ b/content/en/docs/developerportal/maia-plan/create-app/_index.md @@ -1,15 +1,17 @@ --- -title: "Creating an App with Maia Plan" -url: /developerportal/maia-plan/create-app/ -description: "Describes the process of creating an app using Maia Plan." +title: "Creating an App with Maia Spec" +url: /developerportal/maia-spec/create-app/ +description: "Describes the process of creating an app using Maia Spec." weight: 1 +aliases: + - /developerportal/maia-plan/create-app/ --- ## Introduction -Follow the steps in the following pages to create an app with Maia Plan: +Follow the steps in the following pages to create an app with Maia Spec: -1. [Add project context](/developerportal/maia-plan/project-context/). Providing context is the foundation for Maia to build your project plan. Give Maia clear goals, user details, and requirements to generate an accurate app plan. -2. [Define the scope](/developerportal/maia-plan/define-scope/). Work with Maia to refine and detail the project scope, including the goal, success criteria, target users, and requirements. -3. [Generate the plan](/developerportal/maia-plan/generate-plan/). Maia translates your defined scope into a concrete plan, which includes a series of epics and stories. -4. [Start the development](/developerportal/maia-plan/start-development/). Organize and start working on user stories. +1. [Add project context](/developerportal/maia-spec/project-context/). Providing context is the foundation for Maia to build your project plan. Give Maia clear goals, user details, and requirements to generate an accurate app plan. +2. [Define the scope](/developerportal/maia-spec/define-scope/). Work with Maia to refine and detail the project scope, including the goal, success criteria, target users, and requirements. +3. [Generate the plan](/developerportal/maia-spec/generate-plan/). Maia translates your defined scope into a concrete plan, which includes a series of epics and stories. +4. [Start the development](/developerportal/maia-spec/start-development/). Organize and start working on user stories. diff --git a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md index 4de9e2701df..17445cb672a 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/define-scope.md +++ b/content/en/docs/developerportal/maia-plan/create-app/define-scope.md @@ -1,8 +1,10 @@ --- title: "Defining the Scope" -url: /developerportal/maia-plan/define-scope/ -description: "Describes the scope definition step of creating an app with Maia Plan." +url: /developerportal/maia-spec/define-scope/ +description: "Describes the scope definition step of creating an app with Maia Spec." weight: 20 +aliases: + - /developerportal/maia-plan/define-scope/ --- ## Introduction diff --git a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md index aeae7dd2daf..4bacc13889e 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md +++ b/content/en/docs/developerportal/maia-plan/create-app/generate-plan.md @@ -1,8 +1,10 @@ --- title: "Generating the Plan" -url: /developerportal/maia-plan/generate-plan/ -description: "Describes the plan generation step of creating an app with Maia Plan." +url: /developerportal/maia-spec/generate-plan/ +description: "Describes the plan generation step of creating an app with Maia Spec." weight: 30 +aliases: + - /developerportal/maia-plan/generate-plan/ --- ## Introduction diff --git a/content/en/docs/developerportal/maia-plan/create-app/project-context.md b/content/en/docs/developerportal/maia-plan/create-app/project-context.md index b3444ce1cbe..22dae8d0a92 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/project-context.md +++ b/content/en/docs/developerportal/maia-plan/create-app/project-context.md @@ -1,8 +1,10 @@ --- title: "Adding Project Context" -url: /developerportal/maia-plan/project-context/ -description: "Describes the project context step of creating an app with Maia Plan." +url: /developerportal/maia-spec/project-context/ +description: "Describes the project context step of creating an app with Maia Spec." weight: 10 +aliases: + - /developerportal/maia-plan/project-context/ --- ## Introduction diff --git a/content/en/docs/developerportal/maia-plan/create-app/start-development.md b/content/en/docs/developerportal/maia-plan/create-app/start-development.md index 33920a6f4bc..c52a29b8762 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/start-development.md +++ b/content/en/docs/developerportal/maia-plan/create-app/start-development.md @@ -1,8 +1,10 @@ --- title: "Starting the Development" -url: /developerportal/maia-plan/start-development/ -description: "Describes the development step of creating an app with Maia Plan." +url: /developerportal/maia-spec/start-development/ +description: "Describes the development step of creating an app with Maia Spec." weight: 40 +aliases: + - /developerportal/maia-plan/start-development/ --- ## Introduction @@ -15,20 +17,20 @@ After you click **Start Building**, the **Start Development** window is displaye * **Jira** – Use Jira to organize and prioritize your work. To do that, follow the steps in the [Connecting to Jira](#connect-jira) section. {{% alert color="info" %}} - If you start prioritizing your work before Maia is done [finding recommendations](/developerportal/maia-plan/generate-plan/#recommender), recommended components are not displayed in the **Planning** window. + If you start prioritizing your work before Maia is done [finding recommendations](/developerportal/maia-spec/generate-plan/#recommender), recommended components are not displayed in the **Planning** window. {{% /alert %}} -* **Build** – Click the **Open in Studio Pro** button in the **Build** section to open Studio Pro, where you can continue working on the new app. Studio Pro does not currently take into account [recommended components](/developerportal/maia-plan/generate-plan/#recommender). +* **Build** – Click the **Open in Studio Pro** button in the **Build** section to open Studio Pro, where you can continue working on the new app. Studio Pro does not currently take into account [recommended components](/developerportal/maia-spec/generate-plan/#recommender). For details, refer to [Maia Make](/refguide/maia-make/) in the Studio Pro documentation. -## Connecting Maia Plan to Jira {#connect-jira} +## Connecting Maia Spec to Jira {#connect-jira} -The following two sections describe the two main actions you need to take to use Jira as your project management tool in Maia Plan. +The following two sections describe the two main actions you need to take to use Jira as your project management tool in Maia Spec. -### Configuring Jira for Maia Plan +### Configuring Jira for Maia Spec -Follow these steps to configure Jira for use with Maia Plan. +Follow these steps to configure Jira for use with Maia Spec. New Jira projects/spaces: @@ -44,7 +46,7 @@ New Jira projects/spaces: Existing Jira projects/spaces: 1. Open your existing Jira project/space. -2. Select the board you want to use with Maia Plan, or create a new one. +2. Select the board you want to use with Maia Spec, or create a new one. 3. Ensure the board includes a filter for the project's Jira key: * For an existing board: @@ -53,13 +55,13 @@ Existing Jira projects/spaces: 2. Confirm that the filter is set to *project = "your project key"*. * For a new board, select **All work items from your space**. - {{% alert color="info" %}} When you select **All work items from your space**, a consolidated backlog view is created. This view includes work items from all boards in the project, not just those managed through Maia Plan. {{% /alert %}} + {{% alert color="info" %}} When you select **All work items from your space**, a consolidated backlog view is created. This view includes work items from all boards in the project, not just those managed through Maia Spec. {{% /alert %}} -### Configuring Maia Plan for Jira +### Configuring Maia Spec for Jira Before you begin, make sure that the [prerequisites for using Jira](/developerportal/project-management/jira-connector/#prerequisites) are met. -Follow these steps to connect Maia Plan to Jira: +Follow these steps to connect Maia Spec to Jira: 1. In the **Connect Planning Tool** window, select **Jira**. 2. Fill in the information as follows: @@ -70,12 +72,12 @@ Follow these steps to connect Maia Plan to Jira: * **Jira Account** – The login name of a user on the Jira platform with project administration rights. * **API Token** – A valid API token issued by the Jira platform and assigned to the admin user mentioned above. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/). -## Using Jira with Maia Plan +## Using Jira with Maia Spec -After you connect Maia Plan to Jira, you can use Jira as your project management tool: +After you connect Maia Spec to Jira, you can use Jira as your project management tool: -1. In Maia Plan, in the **Start Development** window, set the planning tool to Jira, as previously indicated. -2. Click **Open Jira** to open the connected Jira board from Maia Plan. Your epics and stories are displayed in the Jira backlog. - {{% alert color="warning" %}} The redirection from Maia Plan to team-managed project boards is not currently working as expected. To see your team-managed project board, you need to have the correct URL yourself. This issue does not occur for company-managed project boards, which open correctly from Maia Plan. {{% /alert %}} +1. In Maia Spec, in the **Start Development** window, set the planning tool to Jira, as previously indicated. +2. Click **Open Jira** to open the connected Jira board from Maia Spec. Your epics and stories are displayed in the Jira backlog. + {{% alert color="warning" %}} The redirection from Maia Spec to team-managed project boards is not currently working as expected. To see your team-managed project board, you need to have the correct URL yourself. This issue does not occur for company-managed project boards, which open correctly from Maia Spec. {{% /alert %}} 3. If an active sprint does not already exist, create one in Jira. 4. Move the stories you want to work on from the backlog into the active sprint. The stories in the active sprint are now also available in Studio Pro. diff --git a/content/en/docs/developerportal/maia-plan/create-app/starter-app.md b/content/en/docs/developerportal/maia-plan/create-app/starter-app.md index 02bc038cba8..3449302ac5f 100644 --- a/content/en/docs/developerportal/maia-plan/create-app/starter-app.md +++ b/content/en/docs/developerportal/maia-plan/create-app/starter-app.md @@ -1,9 +1,11 @@ --- title: "Creating an App from a Starter App" -url: /developerportal/maia-plan/using-starter-app/ -description: "Describes how to use a starter app to create an app in Maia Plan." +url: /developerportal/maia-spec/using-starter-app/ +description: "Describes how to use a starter app to create an app in Maia Spec." weight: 50 beta: true +aliases: + - /developerportal/maia-plan/using-starter-app/ --- {{% alert color="info" %}} @@ -12,7 +14,7 @@ This feature is currently in beta. For more information, refer to [Release Statu ## Introduction -You can use a starter app as the basis for Maia Plan to build a project plan. This allows you to use the right branding elements, pre-installed Marketplace modules, and pre-installed integrations. +You can use a starter app as the basis for Maia Spec to build a project plan. This allows you to use the right branding elements, pre-installed Marketplace modules, and pre-installed integrations. ## Creating an App @@ -33,8 +35,8 @@ Follow these steps to have Maia create a project plan based on a starter app: 6. Click **Generate Plan**. This starts the project creation flow. The starter app that's used for the project is displayed in the top bar of the window, just under the project's name. -7. Define the project scope as described in [Defining the Scope](/developerportal/maia-plan/define-scope/). With starter apps, Maia brings in all existing information to the **Define Scope** window. +7. Define the project scope as described in [Defining the Scope](/developerportal/maia-spec/define-scope/). With starter apps, Maia brings in all existing information to the **Define Scope** window. -8. Turn the project scope into a concrete plan, as described in [Generating the Plan](/developerportal/maia-plan/generate-plan/). The side panel displays the resources which are being used from the starter app. +8. Turn the project scope into a concrete plan, as described in [Generating the Plan](/developerportal/maia-spec/generate-plan/). The side panel displays the resources which are being used from the starter app. -9. Select your project management tool and send your project plan to Maia Make, as described in [Starting the Development](/developerportal/maia-plan/start-development/). +9. Select your project management tool and send your project plan to Maia Make, as described in [Starting the Development](/developerportal/maia-spec/start-development/). diff --git a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md index 11f6f74f88e..5fb172945f2 100644 --- a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md +++ b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md @@ -1,13 +1,13 @@ --- -title: "Maia Plan as MCP Server" +title: "Maia Spec as MCP Server" url: /developerportal/maia-plan-mcp/ -description: "Describes how to configure and use Maia Plan as an MCP server to retrieve project scope and solution content." +description: "Describes how to configure and use Maia Spec as an MCP server to retrieve project scope and solution content." weight: 2 --- ## Introduction -The Maia Plan MCP Server provides read-only access to selected Maia Plan artifacts through the Model Context Protocol (MCP). External MCP clients can retrieve plan content, including project scope and project solution, including epics and stories. +The Maia Spec MCP Server provides read-only access to selected Maia Spec artifacts through the Model Context Protocol (MCP). External MCP clients can retrieve plan content, including project scope and project solution, including epics and stories. The MCP server has the following key characteristics: @@ -20,9 +20,9 @@ The MCP server has the following key characteristics: ## Prerequisites -Before you can use the Maia Plan MCP Server, you need the following: +Before you can use the Maia Spec MCP Server, you need the following: -* Access to at least one Maia Plan project in Mendix Portal. +* Access to at least one Maia Spec project in Mendix Portal. * A personal access token (PAT) with the appropriate scopes. For details on how to create and configure your PAT, refer to: * The [Personal Access Tokens](/portal/user-settings/#pat) section of the *User Settings* page @@ -32,20 +32,20 @@ Before you can use the Maia Plan MCP Server, you need the following: ## Configuring the MCP Server {#configure} -To connect your MCP client to the Maia Plan MCP Server, configure the server URL and authentication method. +To connect your MCP client to the Maia Spec MCP Server, configure the server URL and authentication method. ### Server Configuration Configure your MCP client with the following server details: * **Protocol** – The server uses the standard MCP protocol over HTTPS. -* **URL** – The Maia Plan MCP Server endpoint URL, which is `https://plan.home.mendix.com/mcp-server/mcp`. +* **URL** – The Maia Spec MCP Server endpoint URL, which is `https://plan.home.mendix.com/mcp-server/mcp`. ### Authentication {#authentication} -The Maia Plan MCP Server requires authentication using a personal access token (PAT). +The Maia Spec MCP Server requires authentication using a personal access token (PAT). -Create a PAT with the `mx:plan:v1:read` scope for Maia Plan access. For details on how to create and configure your PAT, refer to: +Create a PAT with the `mx:plan:v1:read` scope for Maia Spec access. For details on how to create and configure your PAT, refer to: * The [Personal Access Tokens](/portal/user-settings/#pat) section of the *User Settings* page * [Setting Up Your Personal Access Token](/apidocs-mxsdk/mxsdk/set-up-your-pat/) @@ -72,14 +72,14 @@ The steps to configure your MCP client depend on the client you are using. The f #### Configuring Claude Code -To configure Claude Code to connect to the Maia Plan MCP Server, follow these steps: +To configure Claude Code to connect to the Maia Spec MCP Server, follow these steps: 1. Open your Claude Code configuration file. This is available at the following paths: * Windows: `C:/Users//.claude/settings.json` * macOS/Linux: `~/.claude/settings.json` -2. Add the Maia Plan MCP Server to the list of available MCP servers and specify the server URL and authentication method (using the `MENDIX_TOKEN` environment variable). To do that, add the following server configuration: +2. Add the Maia Spec MCP Server to the list of available MCP servers and specify the server URL and authentication method (using the `MENDIX_TOKEN` environment variable). To do that, add the following server configuration: ```json { @@ -106,14 +106,14 @@ For detailed instructions, refer to the [Claude Code documentation](https://clau #### Configuring Visual Studio Code Copilot {#configuring-visual-studio-code-copilot} -To configure Visual Studio Code Copilot to connect to the Maia Plan MCP server, follow these steps: +To configure Visual Studio Code Copilot to connect to the Maia Spec MCP server, follow these steps: 1. Open the Visual Studio Code MCP configuration file: * User-level: `C:/Users//AppData/Roaming/Code/User/mcp.json` * Workspace-level (optional): `.vscode/mcp.json` -2. Add the Maia Plan MCP Server to the list of available MCP servers and specify the server URL and authentication method (using the `MENDIX_TOKEN` environment variable). To do that, add the following server configuration: +2. Add the Maia Spec MCP Server to the list of available MCP servers and specify the server URL and authentication method (using the `MENDIX_TOKEN` environment variable). To do that, add the following server configuration: ```json { @@ -160,17 +160,17 @@ For other MCP clients, refer to the client documentation for instructions on add ## Available Tools {#tools} -The Maia Plan MCP Server provides the following tools to be used by AI agents for retrieving plan data. You can communicate with AI agents using natural language. +The Maia Spec MCP Server provides the following tools to be used by AI agents for retrieving plan data. You can communicate with AI agents using natural language. ### Get_Project_Plan {#get-plan} -This tool is used by AI agents to search for Maia Plan projects using the project title, the project ID, or keywords. The tool returns a sorted list of accessible plans, along with their UUIDs. You can use a plan's UUID to retrieve plan details using the `Get_Plan_Content` tool. +This tool is used by AI agents to search for Maia Spec projects using the project title, the project ID, or keywords. The tool returns a sorted list of accessible plans, along with their UUIDs. You can use a plan's UUID to retrieve plan details using the `Get_Plan_Content` tool. The tool only returns plans for projects you have permission to view. If you do not have access to a project, it does not appear in the search results. #### Input -Enter one or more of the following to search for a Maia Plan project: +Enter one or more of the following to search for a Maia Spec project: * `projectID` – The project's UUID. * `query` – A search string. The `query` field must not exceed 500 characters, and is best for a title match. @@ -192,7 +192,7 @@ If validation fails, a plain string is returned, not a JSON object. ### Get_Plan_Content {#get-content} -This tool is used by AI agents to retrieve the full content of a specific Maia Plan project by UUID. The tool returns a structured JSON that includes the project scope and/or the solution (epics, stories, acceptance criteria). +This tool is used by AI agents to retrieve the full content of a specific Maia Spec project by UUID. The tool returns a structured JSON that includes the project scope and/or the solution (epics, stories, acceptance criteria). Keep in mind the following: @@ -216,7 +216,7 @@ The tool returns the selected sections as a JSON string. ## How It Works {#how-it-works} -The following steps describe how the Maia Plan MCP Server processes requests: +The following steps describe how the Maia Spec MCP Server processes requests: 1. An MCP client calls one of the available tools and includes an `Authorization` header with a bearer token, which is your personal access token. 2. The server validates the token and identifies you. @@ -226,7 +226,7 @@ The following steps describe how the Maia Plan MCP Server processes requests: ## Security and Access Control {#security} -The Maia Plan MCP Server enforces the following security measures: +The Maia Spec MCP Server enforces the following security measures: * Authentication required – All requests must include a valid bearer token (personal access token) in the authorization header. * Project-level authorization – Access is checked for each project. You can only retrieve data for projects you have permission to view in Mendix Portal. diff --git a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/troubleshooting.md b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/troubleshooting.md index 0c07560dc7e..32641f98e0b 100644 --- a/content/en/docs/developerportal/maia-plan/maia-plan-mcp/troubleshooting.md +++ b/content/en/docs/developerportal/maia-plan/maia-plan-mcp/troubleshooting.md @@ -1,14 +1,14 @@ --- -title: "Troubleshooting Maia Plan as MCP Server" +title: "Troubleshooting Maia Spec as MCP Server" linktitle: "Troubleshooting" url: /developerportal/maia-plan-mcp-troubleshooting/ -description: "Describes how to fix potential Maia Plan as an MCP server issues." +description: "Describes how to fix potential Maia Spec as an MCP server issues." weight: 10 --- ## Introduction -If you encounter issues with Maia Plan as MCP Server, use the following troubleshooting tips to solve them. +If you encounter issues with Maia Spec as MCP Server, use the following troubleshooting tips to solve them. ## 401 or 403 Errors diff --git a/content/en/docs/mendix-portal/maia-portal.md b/content/en/docs/mendix-portal/maia-portal.md index dcfa0398f75..91ad8de1ac3 100644 --- a/content/en/docs/mendix-portal/maia-portal.md +++ b/content/en/docs/mendix-portal/maia-portal.md @@ -13,7 +13,7 @@ Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage {{< figure src="/attachments/developerportal/global-nav/maia-mendix-portal.jpg" alt="Maia in Mendix Portal" width="500" >}} -Maia in Mendix Portal supports the planning, collaboration, and feedback stages of the application lifecycle. For example, you can use Maia Plan to define the scope of a new app, then continue in Studio Pro with Maia Make to build it. For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/). +Maia in Mendix Portal supports the planning, collaboration, and feedback stages of the application lifecycle. For example, you can use Maia Spec to define the scope of a new app, then continue in Studio Pro with Maia Make to build it. For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/). ## Maia Capabilities in Mendix Portal @@ -35,9 +35,9 @@ These are the tasks you can achieve with Maia in Mendix Portal: * **Maia for Feedback** – An AI-assisted tools that help you organize unsorted feedback into groups and themes. This is available on the [Feedback](/developerportal/app-insights/feedback/#organizing-feedback-with-maia) page. -## Maia Plan +## Maia Spec -Maia Plan helps you plan and generate an app from within Mendix Portal. All you need to do is provide project context, review and refine the generated project scope, and approve the solution proposal to start your app development. For detailed steps, refer to [Maia Plan](/developerportal/maia-plan/). +Maia Spec helps you plan and generate an app from within Mendix Portal. All you need to do is provide project context, review and refine the generated project scope, and approve the solution proposal to start your app development. For detailed steps, refer to [Maia Spec](/developerportal/maia-spec/). ## Maia Chat {#maia-chat} diff --git a/content/en/docs/refguide/mendix-ai-assistance/_index.md b/content/en/docs/refguide/mendix-ai-assistance/_index.md index 1870da51fbe..6a43a200575 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/_index.md +++ b/content/en/docs/refguide/mendix-ai-assistance/_index.md @@ -41,7 +41,7 @@ Maia is available at each stage of the application lifecycle. In Studio Pro, Mai | Lifecycle Stage | How Maia Helps | Capabilities | | --- | --- | --- | | Discover and learn | Explains Mendix concepts and answers development questions. |
  • [Maia Learn](/refguide/maia-learn/)
  • [Maia Make](/refguide/maia-make/)
    • | -| Plan and design | Turns an app idea into a project scope, epics, and user stories. |
    • [Maia Plan](/developerportal/maia-plan/)
    • [Create Story with Maia and Refine Story with Maia](/portal/maia/#maia-capabilities-in-mendix-portal)
      • | +| Plan and design | Turns an app idea into a project scope, epics, and user stories. |
      • [Maia Spec](/developerportal/maia-spec/)
      • [Create Story with Maia and Refine Story with Maia](/portal/maia/#maia-capabilities-in-mendix-portal)
        • | | Generate the app | Generates a first version of an app from a description, an image, a PDF, or a plan. |
        • [Start with Maia](/refguide/start-with-maia/)
        • [Maia Make](/refguide/maia-make/)
          • | | Model data | Generates and changes domain models, view entities, enumerations, and OQL queries. |
          • [Maia Make](/refguide/maia-make/)
          • [Domain Models in Maia Make](/refguide/maia-for-domain-model/)
          • [OQL in Maia Make](/refguide/maia-for-oql/)
            • | | Create logic | Generates and changes microflows, recommends the next activity in a flow, and builds validation logic. |
            • [Maia Make](/refguide/maia-make/)
            • [Logic Recommender](/refguide/logic-recommender/)
            • [Validation Assist](/refguide/validation-assist/)
              • | @@ -51,7 +51,7 @@ Maia is available at each stage of the application lifecycle. In Studio Pro, Mai | Understand and get guidance | Explains existing documents and consistency errors, and applies your team conventions. |
              • [Maia Make](/refguide/maia-make/)
              • [Maia Explain](/refguide/maia-explain/)
              • [Agent Instructions](/refguide/maia-agent-instructions/)
              • [Agent Skills](/refguide/maia-agent-skills/)
                • | | Improve quality | Detects anti-patterns, explains their impact, and fixes some of them automatically. Explains and solves consistency errors. |
                • [Maia Make](/refguide/maia-make/)
                • [Best Practice Recommender](/refguide/best-practice-recommender/) | | Localize | Creates and updates translations of the texts in your app (Studio Pro 11.15 and above). |
                  • [Maia Make](/refguide/maia-make/)
                  • [Translation Generator](/refguide/translation-generator/)
                    • | -| Work with external AI agents | Lets external AI agents use Maia capabilities, and lets Maia use your own AI provider. |
                    • [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/)
                    • [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/)
                    • [Custom AI provider](/refguide/maia-make/#custom-provider) (beta)
                      • | +| Work with external AI agents | Lets external AI agents use Maia capabilities, and lets Maia use your own AI provider. |
                      • [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/)
                      • [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/)
                      • [Custom AI provider](/refguide/maia-make/#custom-provider) (beta)
                        • | | Operate and evolve | Summarizes application logs, organizes end-user feedback, and changes existing documents for new requirements. |
                        • [AI Log Summary](/developerportal/maia-operate/ai-log-summary/) (beta)
                        • [Maia for Feedback](/portal/maia/#maia-capabilities-in-mendix-portal)
                        • [Maia Make](/refguide/maia-make/)
                          • | ## Ways to Work with Maia {#ways-to-work} @@ -136,7 +136,7 @@ For an overview of how these options work together, see [Using Maia with Externa ## Maia in Mendix Portal -[Maia in Mendix Portal](/portal/maia/) supports the planning and collaboration stages of the lifecycle. You can use Maia Plan to turn an app idea into a project scope and solution, create and refine user stories, organize end-user feedback, and ask questions in Maia Chat. +[Maia in Mendix Portal](/portal/maia/) supports the planning and collaboration stages of the lifecycle. You can use Maia Spec to turn an app idea into a project scope and solution, create and refine user stories, organize end-user feedback, and ask questions in Maia Chat. ## Maia in Mendix Cloud diff --git a/content/en/docs/refguide/mendix-ai-assistance/agentic-development.md b/content/en/docs/refguide/mendix-ai-assistance/agentic-development.md index 81249946a21..4905ffe0e35 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/agentic-development.md +++ b/content/en/docs/refguide/mendix-ai-assistance/agentic-development.md @@ -113,7 +113,7 @@ The following practices help you get reliable results from Maia and other agents ### Start with Clear Intent -Describe the outcome you want and the context in which it is used. If you work with user stories, use them as input. Maia Make supports story-based development and can generate app artifacts from existing user stories. For larger initiatives, use [Maia Plan](/developerportal/maia-plan/) to define the scope and solution before you build. +Describe the outcome you want and the context in which it is used. If you work with user stories, use them as input. Maia Make supports story-based development and can generate app artifacts from existing user stories. For larger initiatives, use [Maia Spec](/developerportal/maia-spec/) to define the scope and solution before you build. For guidance on how to write effective prompts, see [Prompt Engineering](/agents/prompt-engineering/) and the [Best Practices](/refguide/maia-make/#best-practices) section of *Maia Make Capabilities*. diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md b/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md index df8dfe01797..04ad5172b65 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md @@ -46,7 +46,7 @@ Before you build, you define what the app must do, for whom, and how you measure Maia helps in the following ways: -* [Maia Plan](/developerportal/maia-plan/) – Maia Plan turns your project context, such as goals, target users, requirements, and attached documents, into a project scope. After you approve the scope, Maia generates a solution with epics and user stories. It can also recommend Marketplace components for specific stories. +* [Maia Spec](/developerportal/maia-spec/) – Maia Spec turns your project context, such as goals, target users, requirements, and attached documents, into a project scope. After you approve the scope, Maia generates a solution with epics and user stories. It can also recommend Marketplace components for specific stories. * **Create and Refine a Story with Maia** – Maia can help write new user stories and improve existing ones on the **Board** and **Planning** pages in Mendix Portal. For more information, see [Maia in Mendix Portal](/portal/maia/). You can use the stories from the plan as input when you build with Maia Make, which supports story-based development. Clear user stories with acceptance criteria give Maia better context. @@ -57,7 +57,7 @@ When the scope is clear, use Maia to generate a first version of the app. This g You have the following options: -* From Maia Plan – In Maia Plan, select **Open in Studio Pro** to continue to work on the new app in Studio Pro with Maia Make. For more information, see [Starting the Development](/developerportal/maia-plan/start-development/). +* From Maia Spec – In Maia Spec, select **Open in Studio Pro** to continue to work on the new app in Studio Pro with Maia Make. For more information, see [Starting the Development](/developerportal/maia-spec/start-development/). * [Start with Maia](/refguide/start-with-maia/) – In Studio Pro, select **Start with Maia** as your starting point. Describe your app using a text description and an optional image or PDF. Maia uses this input to generate a domain model, data management overview pages, test data, and a homepage. * Maia Make – In an existing app, describe a new module or feature in the **Maia** pane. Maia then generates the necessary documents. @@ -171,7 +171,7 @@ Some teams use AI coding assistants or their own AI agents next to Studio Pro. S Maia supports these scenarios in the following ways: * [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) – The Studio Pro MCP Server exposes Maia capabilities to external AI agents through the Model Context Protocol (MCP). Changes appear in Studio Pro in real time. -* [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/) – Maia Plan as MCP Server gives external AI agents read-only access to the scope and solution of a Maia Plan project. +* [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/) – Maia Spec as MCP Server gives external AI agents read-only access to the scope and solution of a Maia Spec project. * **Custom AI provider** – The Custom AI provider feature lets Maia use your own LLM provider. This feature is available in Studio Pro 11.12 and above as a beta feature. For more information, see the [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider) section of *Maia Make Capabilities*. For an overview of how these options work together, see [Using Maia with External AI Agents](/refguide/maia-external-agents/). diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md b/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md index ef9e0b7d9cb..db9ed5b66a9 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md @@ -18,7 +18,7 @@ The table below lists the integration options available. Each option connects Ma | --- | --- | --- | --- | | [Maia MCP Client](/refguide/maia-mcp/) | Maia uses tools from external MCP servers. | When a conversation requires information or actions from other systems, such as design assets or a source code platform. | Studio Pro 11.8 | | [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) | External AI agents use Maia capabilities in Studio Pro. | When working with an AI agent or AI coding assistant to create and modify Mendix documents. This is also known as bring your own agent (BYO Agent). | Studio Pro 11.10 | -| [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/) | External AI agents read Maia Plan content. | When an external AI agent needs access to the scope, epics, and stories of a Maia Plan project. | Mendix Portal | +| [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/) | External AI agents read Maia Spec content. | When an external AI agent needs access to the scope, epics, and stories of a Maia Spec project. | Mendix Portal | | [Custom AI provider](/refguide/maia-make/#custom-provider) | Maia uses your LLM provider. | When an organization requires a specific LLM provider or uninterrupted access to Maia without Maia Units. This is also known as bring your own LLM (BYO LLM). | Studio Pro 11.12 (beta) | | [Agent Instructions](/refguide/maia-agent-instructions/) and [Agent Skills](/refguide/maia-agent-skills/) | Shared context for Maia and other agents. | When all agents need to follow the same conventions and use the same domain knowledge. Both follow industry standards, making them compatible with any agentic tool that supports these standards. | Studio Pro 11.11 (Agent SKills), Studio Pro 11.12 (Agent Instructions) | @@ -39,7 +39,7 @@ This approach has the following benefits: * You review the changes in the Studio Pro editors and in the **Errors** pane, in the same way as changes from Maia in Studio Pro. * Agent instructions and agent skills follow the `AGENTS.md` and Agent Skills standards. They work with Maia and with other agentic tools, so your external agent can use the same conventions as Maia. -The Studio Pro MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. Mendix platform MCP servers, such as Maia Plan as MCP Server, require authentication with your Mendix account. +The Studio Pro MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. Mendix platform MCP servers, such as Maia Spec as MCP Server, require authentication with your Mendix account. When you use an external agent, the agent uses tokens from your own LLM provider account. Usage and billing are managed by your LLM provider, not by Mendix. @@ -65,8 +65,8 @@ The following example shows how you can combine the options. A team plans an app in Mendix Portal and uses an AI coding assistant to implement the stories in Studio Pro. -1. Create a plan in [Maia Plan](/developerportal/maia-plan/). Review the scope, epics, and stories. -2. In your AI coding assistant, configure the [Maia Plan MCP Server](/developerportal/maia-plan-mcp/#configure) with a personal access token that has the `mx:plan:v1:read` scope. +1. Create a plan in [Maia Spec](/developerportal/maia-spec/). Review the scope, epics, and stories. +2. In your AI coding assistant, configure the [Maia Spec MCP Server](/developerportal/maia-plan-mcp/#configure) with a personal access token that has the `mx:plan:v1:read` scope. 3. Open the app in Studio Pro and [enable the Studio Pro MCP Server](/refguide/studio-pro-mcp-server/#enabling-the-mcp-server). Connect your AI coding assistant to it. 4. Add an [AGENTS.md](/refguide/maia-agent-instructions/) file with your team conventions, such as naming rules and the modules that the agent must not change. Agent instructions guide the agent, but they do not enforce restrictions, so check the result in step 6. 5. In your AI coding assistant, ask the agent to get one story from the plan and implement it in a specific module. @@ -90,6 +90,6 @@ Keep the following points in mind when you connect external AI tools: * [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) * [Maia MCP Client](/refguide/maia-mcp/) -* [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/) +* [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/) * [Agentic and Model-Driven Development](/refguide/agentic-development/) * [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md index 159ad006a3b..87407e6120f 100644 --- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md +++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md @@ -12,7 +12,7 @@ description: "Describes the features in Studio Pro MCP Server." {{% alert color="info" %}} This feature is available from Studio Pro 11.10. -To use Studio Pro MCP Server, you need an internet connection. The MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. To use Mendix platform MCP servers, such as [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/), you need to authenticate with your Mendix account. +To use Studio Pro MCP Server, you need an internet connection. The MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. To use Mendix platform MCP servers, such as [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/), you need to authenticate with your Mendix account. {{% /alert %}} Studio Pro MCP Server enables bring your own agent (BYO Agent) capabilities, allowing you to use Maia's capabilities directly from external clients, including AI coding assistants, agents, and other MCP-based LLM tools. @@ -44,7 +44,7 @@ The external client works with Mendix documents, such as domain models and micro Use the Studio Pro MCP Server in the following situations: * You use an AI coding assistant for other work, such as code in other repositories, documentation, or tickets. With the MCP Server, you can use the same assistant for your Mendix app. -* Your agent has access to other MCP servers, such as [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). The agent can use information from these sources, then change your app through the Studio Pro MCP Server. +* Your agent has access to other MCP servers, such as [Maia Spec as MCP Server](/developerportal/maia-plan-mcp/). The agent can use information from these sources, then change your app through the Studio Pro MCP Server. * You need an alternative to Maia Units. Requests from an external client use your own LLM provider account. For more information, see the [Maia Usage Limits](/refguide/mendix-ai-assistance/#maia-usage) section of *Mendix AI Assistance (Maia)*. ## Enabling the MCP Server diff --git a/content/en/docs/releasenotes/developer-portal/2026.md b/content/en/docs/releasenotes/developer-portal/2026.md index 276c921ea0f..d9413b0a354 100644 --- a/content/en/docs/releasenotes/developer-portal/2026.md +++ b/content/en/docs/releasenotes/developer-portal/2026.md @@ -12,7 +12,7 @@ weight: 1 #### New Features -* You can now use a starter app as the basis for Maia Plan to build a project plan. This allows you to bring in the right branding elements, pre-installed Marketplace modules, and pre-installed integrations from the start. For details, refer to [Creating an App from a Starter App](/developerportal/maia-plan/using-starter-app/). +* You can now use a starter app as the basis for Maia Plan to build a project plan. This allows you to bring in the right branding elements, pre-installed Marketplace modules, and pre-installed integrations from the start. For details, refer to [Creating an App from a Starter App](/developerportal/maia-spec/using-starter-app/). ### October 15, 2026 @@ -40,7 +40,7 @@ weight: 1 #### Fixes -* We have made the following fixes in [Maia Plan](/developerportal/maia-plan/): +* We have made the following fixes in [Maia Plan](/developerportal/maia-spec/): * We have fixed errors that occurred while loading the content of the **Define Scope** window. * We have fixed an issue that prevented you from changing the story description format. @@ -121,7 +121,7 @@ weight: 1 #### New Features -* You can now connect to [Maia Plan](/developerportal/maia-plan/) as an MCP server. This allows you to retrieve project plans and plan content using MCP clients such as Claude Code. For details, refer to [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). +* You can now connect to [Maia Plan](/developerportal/maia-spec/) as an MCP server. This allows you to retrieve project plans and plan content using MCP clients such as Claude Code. For details, refer to [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). ### June 28, 2026 @@ -133,7 +133,7 @@ weight: 1 #### New Features -* You can now use Jira as your planning tool when creating an app with [Maia Plan](/developerportal/maia-plan/). During the **Start Development** step, you can choose between the Mendix Planning Board or Jira to organize and prioritize your work. For details, refer to the [Connecting Maia Plan to Jira](/developerportal/maia-plan/start-development/#connect-jira) section in *Starting the Development*. +* You can now use Jira as your planning tool when creating an app with [Maia Plan](/developerportal/maia-spec/). During the **Start Development** step, you can choose between the Mendix Planning Board or Jira to organize and prioritize your work. For details, refer to the [Connecting Maia Plan to Jira](/developerportal/maia-spec/start-development/#connect-jira) section in *Starting the Development*. ### June 14, 2026 @@ -147,7 +147,7 @@ weight: 1 #### Fixes -* We have fixed an issue in [Maia Plan](/developerportal/maia-plan/) where accessing a plan after some time had passed since its creation resulted in an error. You can safely access the plan both immediately after creation and at any later time, through the **Apps** page in Mendix Portal or through a deep link. +* We have fixed an issue in [Maia Plan](/developerportal/maia-spec/) where accessing a plan after some time had passed since its creation resulted in an error. You can safely access the plan both immediately after creation and at any later time, through the **Apps** page in Mendix Portal or through a deep link. ### May 21, 2026 @@ -161,7 +161,7 @@ weight: 1 #### Improvements -* In an effort to provide a seamless app creation experience, we have updated the [Maia Plan](/developerportal/maia-plan/) project creation flow. Everything works the same, but the step layout and progression are now aligned to the general Mendix Portal experience that you might already be used to. +* In an effort to provide a seamless app creation experience, we have updated the [Maia Plan](/developerportal/maia-spec/) project creation flow. Everything works the same, but the step layout and progression are now aligned to the general Mendix Portal experience that you might already be used to. #### Fixes @@ -174,7 +174,7 @@ weight: 1 #### New Features -* Maia Plan now recommends Marketplace components for stories that can benefit from them during implementation. For details, refer to the [Recommended Marketplace Components](/developerportal/maia-plan/generate-plan/#recommender) section in *Maia Plan*. +* Maia Plan now recommends Marketplace components for stories that can benefit from them during implementation. For details, refer to the [Recommended Marketplace Components](/developerportal/maia-spec/generate-plan/#recommender) section in *Maia Plan*. ## March 2026 @@ -182,7 +182,7 @@ weight: 1 #### New Features -* Maia Plan is now generally available (GA). Refer to [Maia Plan](/developerportal/maia-plan/) for details on how Maia can assist you in creating your app. +* Maia Plan is now generally available (GA). Refer to [Maia Plan](/developerportal/maia-spec/) for details on how Maia can assist you in creating your app. ### March 29, 2026 @@ -197,7 +197,7 @@ weight: 1 #### New Features * You can now ask Maia to create a project plan for your new app. To do that, simply choose the **Plan & Build with Maia** option at the start of the app creation workflow, and provide as much information as you can about what you want from your future app. Maia will then suggest the basis for your app, such as goals, target users, requirements, epics, and stories, which you can edit to suit your needs. - For details, refer to [Maia Plan](/developerportal/maia-plan/). + For details, refer to [Maia Plan](/developerportal/maia-spec/). ### March 1, 2026 diff --git a/content/en/docs/releasenotes/feature-release-calendar/_index.md b/content/en/docs/releasenotes/feature-release-calendar/_index.md index 2baae054e5d..fb3b08fc3ac 100644 --- a/content/en/docs/releasenotes/feature-release-calendar/_index.md +++ b/content/en/docs/releasenotes/feature-release-calendar/_index.md @@ -45,8 +45,8 @@ General Availability means that a feature is available for all users. This type | Capability or Feature | Expected Release | | --- | --- | -| Maia Plan
                          • Starter app support
                          • Marketplace recommendations
                          | Public Beta: Mx 11.8
                          General Availability: Mx 11.9 | -| Maia Plan
                          • Versioning, iterations and multi-user collaboration
                          • Jira integration
                          | General Availability: Mx 11.12 | +| Maia Spec
                          • Starter app support
                          • Marketplace recommendations
                          | Public Beta: Mx 11.8
                          General Availability: Mx 11.9 | +| Maia Spec
                          • Versioning, iterations and multi-user collaboration
                          • Jira integration
                          | General Availability: Mx 11.12 | | Maia: Text to OQL | Public Beta: Q2 2025
                          General Availability: Q4 2025 | | Maia: Generate test data | Private Beta: 2026 | | Maia: Convert Feedback to story | General Availability: Mx 11.9 |