Mendix MCP connector
The Mendix connector brings Mendix projects, roles, backups, build packages, catalog applications and audit logs into Claude, ChatGPT, Cursor and Microsoft Copilot, so your team can ask about them and act on them in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
List the build packages for the customer portal project.
Working in Mendix with Elaichi
-
List all Mendix account projects
-
List all Mendix account roles
-
Get single Mendix account role by ID
How to connect Mendix to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Mendix MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Mendix MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Mendix MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Mendix MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Mendix MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Mendix to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Mendix through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Mendix is logged.
-
Platform
See every Mendix project in one view
Ask which projects exist in the Mendix account and which roles hold access to them before a steering meeting, instead of clicking through each one.
-
Operations
Take a snapshot before a risky change
Create a backup snapshot of an environment, check it exists, and start a restore if a deployment goes wrong, all by asking.
-
Release management
Find the build package that is ready to ship
List the build packages for a project, look up the file for the one you need, and clear out old packages nobody will deploy.
-
Security
Answer an auditor from the Mendix audit log
Pull audit log entries and the audit log chain for a period and have the agent summarize who changed what, ready to hand over.
-
Governance
Keep the Mendix catalog accurate
Register a new application in the catalog, update its details when ownership changes, and remove entries for applications that were retired.
-
IT administration
Review account roles before onboarding
List the roles in the Mendix account and read what a single role allows before deciding which one a new team member should get.
Try asking
- “List the build packages for the customer portal project.”
- “Create a backup snapshot of production before tonight's deploy.”
- “Summarize this week's Mendix audit log entries for me.”
What connecting Mendix gets you
6 screens from Elaichi, each doing one job for your Mendix account.
Ask Elaichi to work across your apps.
List the build packages for the customer portal project.
Create a backup snapshot of production before tonight's deploy.
Summarize this week's Mendix audit log entries for me.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Plain questions get live answers from Mendix.
Three starter prompts pull answers from projects, backup snapshots and build packages as they are now.
Copy the endpoint
AI apps
One endpoint connects Mendix to every client.
Claude, ChatGPT and Cursor reach Mendix through one governed endpoint, no SDK, no shared key.
Tool catalog
175 Mendix tools, ready without writing code.
Projects, roles, backups, build packages, catalog applications and audit logs, covered out of the box.
Toolboxes
Every team gets its own Mendix toolbox.
Operations keeps backups, release management keeps build packages, security keeps the audit log.
Shared connections
Share a Mendix connection, never the API key.
Teammates work through the connection you made without ever seeing the credential behind it.
Audit log
Know who restored which Mendix backup, and when.
Every call lands in an append-only log with who, what, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Mendix digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Mendix
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Mendix
Queued
Workflows
A schedule starts Mendix work, people approve it.
New audit log entries are fetched, grouped, drafted into a digest, approved and posted back.
Mendix health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Backup snapshots
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Platform 34%
Operations 27%
Release 21%
Security 18%
Collections and dashboards
Mendix health numbers refresh without anyone asking.
Four metrics, fourteen days of build packages created, and a breakdown by team, on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Mendix
All three can connect Mendix to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Mendix tools | Allow or restrict single Mendix tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Mendix call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Mendix tools for your AI agents
175 tools are ready to call through Elaichi's MCP endpoint the moment you connect Mendix, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Mendix to Claude?
Open Elaichi, choose Mendix, and paste a Mendix API key when asked. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp, and Mendix is available in your chats.
Does Mendix work with ChatGPT and Cursor as well as Claude?
Yes. Once Mendix is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Mendix once and every client can use it.
What can an AI agent actually do with my Mendix data?
With Mendix connected, an agent can list your projects and account roles, read the audit log, create and restore backup snapshots, list and create build packages, and keep catalog applications up to date. Short, concrete asks work best, such as "take a snapshot of the production environment" rather than a long paragraph.
Does connecting Mendix give the AI access to every project in the account?
No. A Mendix connection can only reach what the Mendix API key behind it is allowed to reach, and every person still signs in to Elaichi as themselves. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Mendix itself permits.
Can I stop an agent from deleting or changing things in Mendix?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting Mendix backup snapshots or build packages for a role or for one person while leaving reading alone. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Mendix connection when someone leaves?
Offboarding a person in Elaichi ends their access to Mendix at once, across every client they used. A shared Mendix connection keeps working for everyone else on the team. If you want Mendix gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Mendix MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Mendix is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Mendix?
Yes. Both let Claude, ChatGPT or Cursor use Mendix. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Mendix call.
How is Elaichi different from Composio for Mendix?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Mendix: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Mendix in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot