MCP Client
Overview
Mendix MCP Client Module
Consume external tools and prompts from your enterprise landscape within your Mendix app using the Mendix MCP Client module.
The Mendix MCP Client Module provides an easy low-code capability to set up a connection to an MCP Server from a Mendix app using the Model Context Protocol (MCP). Using the module, resources such as tools and prompts can easily be discovered and used within a Mendix application, without any custom integrations to third-party systems. The Mendix MCP Client module builds a bridge between Mendix and MCP server applications such as other Mendix apps, through the MCP Java SDK.
With the current implementation, it is possible to:
- Discover prompts and tools from servers.
- Consume reusable prompts including the ability to use prompt arguments
- Call external tools as part of an LLM interaction (if combined with GenAI Commons)
Check out the GenAI Showcase App for an example implementation.
Contact Us
For support and questions, feel free to reach out via email: genai-components-feedback@mendix.com or Community Slack.
Documentation
Mendix MCP Client Module
Support
This module is based on Mendix 10.24.13 and uses MCP Java SDK 0.16.0 that supports MCP Protocol version 2024-11-05 and 2025-03-26.
How to use
For an example implementation check out the GenAI Showcase App.
Known Limitations
- Tools and prompt messages can only return String content.
- Only HTTP+SSE transport is currently supported to communicate with MCP servers.
Releases
* We added support for Streamable HTTP transport method which can be enabled when using the 2025-03-26 protocol version during creation of the client connection.
* The Create MCP Client action now throws an error when it cannot connect to the server. This can be used to implement custom error handling (for example to change the authentication headers). We recommend to add error handling in all places where this action is implemented.
* We added more debug logging to the List Tools and List Prompts actions, to understand what the server returned.
* We added ConnectionTimeOutInSeconds to the MCPServerConfiguration entity to change the timeout settings. This can happen either in the UI via the config page or when creating the connection in a microflow. The default timeout is 10 seconds.
* The module was upgraded to 10.24.13.
Small internal change for compatibility with new ConversationalUI v5.3.0 capability: Observability for AI Traces
Static image widget instances were replaced with Image widgets.
MCP tool sync process has been improved. Sync process is added to task queue and completed in the background