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

 

The Mendix MCP Server Module provides easy low-code capability to set up MCP Server within a Mendix app. Using the MCP Server resources can easily be made available to other applications that support the Model Context Protocol (MCP). The Mendix MCP Server module interacts 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

 

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.

 

The MCP Server module glues the actual server to microflows in the applications. When setting up the MCP Server configuration each prompt and tool is linked with a microflow that receives input from the client and return a result based on the MCP schema definition. To expose a prompt or tool

  • For a prompt; create a microflow returning a PromptMessage entity. Input parameters can be defined using basic types as string and numbers.
  • For a tool; create a microflow accepting input parameters and process the request. It should return a TextContent object.
  • Initiate the MCP Server and add tools and prompts in a microflow that is called in the After Startup microflow of your app or in your custom logic triggered by a user.
  • Run the application
  • For testing you can use any MCP client such as MCP Inspector.

 

Known limitations

  • Tools can return one TextContent result.
  • Prompts can return one PromptMessage result.
  • Mendix runtime doesn't support async requests, to keep the client connection alive the request thread is blocked for 15 minutes.
  • Authentication is not implemented (yet).

Releases

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