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.

Documentation

Mendix MCP Server Module

Support

This module is based on Mendix 10.21.1 and uses MCP Java SDK 0.8.1 that supports MCP Protocol version 2024-11-05.

 

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.
  • The client connection remains active for only 15 minutes, as the Mendix runtime currently does not support async requests.
  • Running an MCP Server is currently only supported on single-instance environments.
  • User authorization can currently only be applied on request but not at the tool/prompt level. As a result, the current user is not available within tool/prompt microflows, and entity access or XPath constraints can not be enabled out of the box. This is due to the capabilities offered by the official MCP Java SDK which does not support reusing a Mendix user session in the executed tools/prompts.

 

Releases

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