MCP Server

Content Type: Module
Categories: Connectors,Data,Artificial Intelligence

Overview

Mendix MCP Server Module

Make your Mendix business logic available to any agent in your enterprise landscape with the Mendix MCP Server module.

 

The Mendix MCP Server Module provides easy low-code capability to set up MCP Server within a Mendix app using the Model Context Protocol (MCP). Using the MCP Server resources can easily be made available to other applications that support MCP. The Mendix MCP Server module bridges the Mendix model and the Java MCP SDK. With the current implementation it is possible to:

  • Expose reusable prompts including the ability to use prompt parameters
  • List and run actions implemented in the application as tools

 

Check out the GenAI Showcase App for an example implementation with Claude Desktop and the blog post: How to use MCP to bring Mendix Business Logic into Claude for Desktop for more details.

 

Contact Us

For support and questions, feel free to reach out via email: genai-components-feedback@mendix.com or Community Slack.

Documentation

Mendix MCP Server Module

 

Support

This module is based on Mendix 10.24.13 and uses MCP Java SDK 0.16.0 that supports MCP Protocol version 2025-03-26.

 

How to use

For an example implementation with Claude Desktop, check out the GenAI Showcase App. Also see the blog post for more information: How to use MCP to bring Mendix Business Logic into Claude for Desktop.

 

Known Limitations

  • Tools can only return String values, either directly as String type or using the TextContent entity.
  • Prompts can only return a single message.
  • Running an MCP Server is currently only supported on single-instance environments.

 

 

 

Releases

Version: 4.0.0
Framework Version: 10.24.13
Release Notes:

* We added support for Streamable HTTP transport which can be enabled when passing a newer protocol version to the server config. Note that the old version v2024-11-05 which used the legacy HTTP+SSE transport is no longer available.

* With the new transport, a bug got fixed that caused large payload tool results to fail.

* We fixed an issue where the Mendix / MCP session was not properly reused if authentication was enabled. Especially in locally running apps this resulted in errors when the maximum number of sessions was reached. * A bug was fixed that blocked multiple servers to run in the same Mendix app simultaneously. Previously, the last started server overwrote the tools from the ones started before.

* We improved value parsing for tool microflow calls for automatic schema creation, so that also non-string datatypes are converted correctly. We added more detailed descriptions for datetime parameters specifically, so the model better understands how to pass the values.

* Note that the path of MCP servers are now validated and cannot be "mcp".

Version: 3.2.0
Framework Version: 10.24.13
Release Notes:

The MCP SDK version was upgraded to 0.16.0. Also, a thread sleep setting was removed from the request handler, since this is handled by Studio Pro Runtime instead.

Version: 3.1.0
Framework Version: 10.24.0
Release Notes:

We enabled the user (and session) to be in scope of the tool and prompt microflows. If the user was authenticated (via the authentication microflow), they are now accessible as variable in the tool and prompt microflows. This makes it possible to apply role (and user) based access control to tools/prompts, for example by applying entity access in the microflow.

Version: 3.0.0
Framework Version: 10.24.0
Release Notes: * The MCP Java SDK version was upgraded to 0.11.1. * A bug was fixed where the required boolean was not set for automatic schema tool creation. * Module has been upgraded to Mendix Studio Pro version 10.24
Version: 2.1.1
Framework Version: 10.21.1
Release Notes: * We fixed a bug in the java imports to remove an unnecessary dependency. Release notes from 2.1.0: * We extended the MCP HTTP handler to support HEAD commands which is used by Langflow (and Langflow implementors like Rapidminer AI Cloud) to validate the MCP server URL. * The schema input for the AddTool action is now optional: if left empty, the schema gets created automatically based on the selected microflow's input. If a value is passed, it will overwrite the schema attribute of the tool. * Tool microflows can now also return a value of type String (as alternative to a TextContent object).
Version: 2.0.0
Framework Version: 10.21.1
Release Notes: * When creating an MCP Server, you can now specify an authentication microflow that gets executed once a client starts the connection. The microflow can only have MCPServer or HttpRequest as input and needs to return a System.User. Inside of the microflow you can apply your custom authentication method (e.g., basic auth, OAuth etc.). If no user is returned, access to the MCP Server gets blocked. Note: at the moment the current User (that was authorized) is not in scope inside of the tool/prompt microflows. * When creating an MCP Server you now need to specify the MCP version for which the server is started. Currently, only 2024_11_05 is allowed. The MCP client should be compatible with the same version. * An Example Implementations folder was added to the module for inspiration. It currently contains starting a server with an authentication microflow as well as adding a tool and prompt to it.
Version: 1.0.0
Framework Version: 10.21.1
Release Notes: MCP Server - publish your microflows & data as MCP services