# 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.

Source: https://elaichi.ai/connectors/mendix/

## Facts

| | |
| --- | --- |
| Application | Mendix |
| Category | Application Development |
| AI tools | 175 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Mendix is connected

- 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.

## Connect Mendix in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Mendix.
2. Optionally set Share with, then press Connect.
3. Paste a Mendix API key. One person generates a token in Mendix and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Mendix tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Mendix MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Mendix MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Mendix tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Mendix through Elaichi

### See every Mendix project in one view

Platform. 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.

### Take a snapshot before a risky change

Operations. Create a backup snapshot of an environment, check it exists, and start a restore if a deployment goes wrong, all by asking.

### Find the build package that is ready to ship

Release management. List the build packages for a project, look up the file for the one you need, and clear out old packages nobody will deploy.

### Answer an auditor from the Mendix audit log

Security. Pull audit log entries and the audit log chain for a period and have the agent summarize who changed what, ready to hand over.

### Keep the Mendix catalog accurate

Governance. Register a new application in the catalog, update its details when ownership changes, and remove entries for applications that were retired.

### Review account roles before onboarding

IT administration. List the roles in the Mendix account and read what a single role allows before deciding which one a new team member should get.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Mendix connection?

Yes. One person connects Mendix in Elaichi and shares the connection with a team, and nobody else ever handles the Mendix API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who created a snapshot or deleted a build package.

### 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.

## All 175 Mendix tools

Every tool below is callable through https://api.elaichi.ai/mcp once Mendix is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Mendix account projects** (List). Get a list of company-owned projects. Returns a list of projects owned by the company of the requesting user. Inactive projects are only returned if the requesting user is a Mendix Admin. Every request must be authenticated through a Personal Access Token containing the mx:app:metadata:read scope. [Projects API v2: GET /v2/accounts/{account-id}/projects. Needs a Personal Access Token.] Required: account_id.
- **List all Mendix account roles** (List). Get a list of project roles for a specified account. Returns a list of project roles for a specified account or company. The output is restricted based on the authorization of the calling user. The calling user must be a member of the specified company. Every request must be authenticated through a Personal Access Token containing the mx:app:roles:read scope. [Projects API v2: GET /v2/accounts/{account-id}/roles. Needs a Personal Access Token.] Required: account_id.
- **Get single Mendix account role by ID** (Get). Get all details of a specific project role. [Projects API v2: GET /v2/roles/{role-id}. Needs a Personal Access Token.] The id is the role-id. Required: id.
- **List all Mendix audit log chain** (List). Retrieve audit logs chain. Retrieves a chain of audit logs for a specific owner. If a cursor is not provided, the first page is returned. Output is ordered chronologically, from newest to oldest. Authorization Authorization: Bearer or Authorization: MxToken Requires the mx:audit-logging:read scope. [Audit Logging API: GET /v1/logs-chain. Needs a Personal Access Token.]
- **List all Mendix audit logs** (List). Retrieve audit logs. Retrieves a list of audit logs filtered by Owner ID with pagination, sorting, and filtering support. The Owner ID is derived from the token used in the request. Logs cannot be retrieved for an Owner ID that is different to the one in the token. [Audit Logging API: GET /v1/logs. Needs a Personal Access Token.]
- **Create a Mendix backup restore** (Create). Request a restore of a snapshot to an environment. Restores a snapshot (of any environment of the same app) to a stopped environment. Mendix Cloud only. [Backups API v2: POST /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/restores. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: project_id, environment_id, source_snapshot_id.
- **Get single Mendix backup restore by ID** (Get). Request status of a snapshot restore. Checks the status of a restore request. [Backups API v2: GET /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/restores/{RestoreId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the RestoreId. Required: id, project_id, environment_id.
- **Create a Mendix backup snapshot archive** (Create). Request creation of a snapshot archive. Requests a downloadable archive of a snapshot; poll it with the archive_id until url is set. [Backups API v2: POST /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots/{SnapshotId}/archives. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: project_id, environment_id, snapshot_id.
- **Get single Mendix backup snapshot archive by ID** (Get). Request status of creation of an archive. Gets the status of an archive creation; when completed, url links to the backup. [Backups API v2: GET /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots/{SnapshotId}/archives/{ArchiveId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the ArchiveId. Required: id, project_id, environment_id, snapshot_id.
- **List all Mendix backup snapshots** (List). List environment snapshots. Lists the snapshots (backups) of an environment, newest first, paged with offset and limit. [Backups API v2: GET /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: project_id, environment_id.
- **Create a Mendix backup snapshot** (Create). Request creation of an environment snapshot. Requests a snapshot of an environment; poll its state with the snapshot_id. Send at least an empty JSON object. [Backups API v2: POST /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: project_id, environment_id.
- **Get single Mendix backup snapshot by ID** (Get). Request status of creation of a snapshot. Gets a snapshot and the current status of its creation. [Backups API v2: GET /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots/{SnapshotId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the SnapshotId. Required: id, project_id, environment_id.
- **Update a Mendix backup snapshot by ID** (Update). Update an existing snapshot. Sets a new comment on a snapshot. [Backups API v2: PUT /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots/{SnapshotId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the SnapshotId. Required: id, project_id, environment_id, comment.
- **Delete a Mendix backup snapshot by ID** (Delete). Delete an existing snapshot. Deletes a snapshot. [Backups API v2: DELETE /api/v2/apps/{ProjectId}/environments/{EnvironmentId}/snapshots/{SnapshotId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the SnapshotId. Required: id, project_id, environment_id.
- **List all Mendix build packages** (List). Retrieve packages. Retrieves all deployment packages available for an app. [Build API: GET /api/1/apps/{AppId}/packages. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: app_id.
- **Create a Mendix build package** (Create). Start building deployment package. Starts building a deployment package from the team server repository of an app (for a Free App it also deploys the package). Poll Retrieve Package until Status is Succeeded. [Build API: POST /api/1/apps/{AppId}/packages. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: app_id, Branch, Revision, Version.
- **Get single Mendix build package by ID** (Get). Retrieve package. Retrieves a deployment package of an app. [Build API: GET /api/1/apps/{AppId}/packages/{PackageId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the PackageId. Required: id, app_id.
- **Delete a Mendix build package by ID** (Delete). Delete package. Deletes a deployment package of an app. [Build API: DELETE /api/1/apps/{AppId}/packages/{PackageId}. Accepts a Personal Access Token or a Mendix API key (username + API key).] The id is the PackageId. Required: id, app_id.
- **Mendix build packages lookup file** (Action). DEPRECATED: Download package. Downloads a deployment package file (deprecated: use Retrieve Package with url=true). [Build API: GET /api/1/apps/{AppId}/packages/{PackageId}/download. Accepts a Personal Access Token or a Mendix API key (username + API key).] Required: app_id, package_id.
- **Create a Mendix catalog application** (Create). Registers an application. [Catalog Registration API v5: POST /rest/registration/v5/applications. Needs a Personal Access Token.] Required: name.
- **List all Mendix catalog applications** (List). Retrieves all the applications from users company. [Catalog Registration API v5: GET /rest/registration/v5/applications. Needs a Personal Access Token.]
- **Get single Mendix catalog application by ID** (Get). Retrieves the details of a particular application. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}. Needs a Personal Access Token.] The id is the AppUUID. Required: id.
- **Delete a Mendix catalog application by ID** (Delete). Deletes the specified application and all environments and endpoints associated to it. Deleting an application can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: DELETE /rest/registration/v5/applications/{AppUUID}. Needs a Personal Access Token.] The id is the AppUUID. Required: id.
- **Update a Mendix catalog application by ID** (Update). Register a new application or update an existing application at the given UUID. Some PUT operations can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: PUT /rest/registration/v5/applications/{AppUUID}. Needs a Personal Access Token.] The id is the AppUUID. Required: id, name.
- **Mendix catalog consumed endpoints bulk update** (Update). Registers all consumed endpoints for the specified app and environment. Some PUT operations can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: PUT /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/consumed-endpoints. Needs a Personal Access Token.] Required: app_uuid, environment_uuid, endpoints.
- **List all Mendix catalog consumed endpoints** (List). Returns all consumed endpoints for the specified environment. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/consumed-endpoints. Needs a Personal Access Token.] Required: app_uuid, environment_uuid.
- **Get single Mendix catalog consumed endpoint by ID** (Get). Return details of specified consumed endpoint. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/consumed-endpoints/{EndpointUUID}. Needs a Personal Access Token.] The id is the EndpointUUID. Required: id, app_uuid, environment_uuid.
- **Mendix catalog dependencies convert** (Convert). Transforms contents of the dependencies.json file for your Mendix app into request bodies for the PUT published/consumed-endpoints operations of this API. For this call the contents of the dependencies.json file have to be included. The dependencies.json file for your Mendix app is usually located in your project folder in the deploymentmodel directory. Contents of this file must be included in escaped JSON format. [Catalog Registration API v5: POST /rest/registration/v5/transform/dependenciesjson. Needs a Personal Access Token.] Required: dependenciesJsonString.
- **Get single Mendix catalog endpoint by ID** (Get). Retrieves the details of the specified endpoint. [Catalog Search API v5: GET /rest/search/v5/endpoints/{EndpointUUID}. Needs a Personal Access Token.] The id is the EndpointUUID. Required: id.
- **Create a Mendix catalog environment** (Create). Registers an environment for the specified application. [Catalog Registration API v5: POST /rest/registration/v5/applications/{AppUUID}/environments. Needs a Personal Access Token.] Required: app_uuid, name, location, type.
- **List all Mendix catalog environments** (List). Retrieves the details of all environments of an application. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments. Needs a Personal Access Token.] Required: app_uuid.
- **Get single Mendix catalog environment by ID** (Get). Retrieves the details of a particular environment of an application. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}. Needs a Personal Access Token.] The id is the EnvironmentUUID. Required: id, app_uuid.
- **Delete a Mendix catalog environment by ID** (Delete). Deletes the specified environment. Deleting an environment can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: DELETE /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}. Needs a Personal Access Token.] The id is the EnvironmentUUID. Required: id, app_uuid.
- **Update a Mendix catalog environment by ID** (Update). Registers or updates a specific environment at the given UUID. Currently registered environments are overwritten with the values provided in this request body. Some PUT operations can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: PUT /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}. Needs a Personal Access Token.] The id is the EnvironmentUUID. Required: id, app_uuid, name, location, type.
- **Mendix catalog published endpoints bulk update** (Update). Registers all published endpoints for the specified app UUID and environment UUID. Some PUT operations can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: PUT /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints. Needs a Personal Access Token.] Required: app_uuid, environment_uuid, endpoints.
- **Create a Mendix catalog published endpoint** (Create). Registers a published endpoint for the specified app and environment. [Catalog Registration API v5: POST /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints. Needs a Personal Access Token.] Required: app_uuid, environment_uuid, path, serviceVersion.
- **List all Mendix catalog published endpoints** (List). Returns all published endpoints for the specified environment. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints. Needs a Personal Access Token.] Required: app_uuid, environment_uuid.
- **Get single Mendix catalog published endpoint by ID** (Get). Returns details of the specified published endpoint. [Catalog Registration API v5: GET /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints/{EndpointUUID}. Needs a Personal Access Token.] The id is the EndpointUUID. Required: id, app_uuid, environment_uuid.
- **Delete a Mendix catalog published endpoint by ID** (Delete). Deletes the specified published endpoint. Deleting an endpoint can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: DELETE /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints/{EndpointUUID}. Needs a Personal Access Token.] The id is the EndpointUUID. Required: id, app_uuid, environment_uuid.
- **Update a Mendix catalog published endpoint by ID** (Update). Updates the details of the specified published endpoint. Will create the published endpoint if it does not exist yet. Some PUT operations can only be done by the owner of the resource’s application, company admins, or Catalog curators. [Catalog Registration API v5: PUT /rest/registration/v5/applications/{AppUUID}/environments/{EnvironmentUUID}/published-endpoints/{EndpointUUID}. Needs a Personal Access Token.] The id is the EndpointUUID. Required: id, app_uuid, environment_uuid, path, serviceVersion.
- **List all Mendix catalog search** (List). Search in the Catalog based on the query string and specified filters. [Catalog Search API v5: GET /rest/search/v5/data. Needs a Personal Access Token.]
- **List all Mendix categories** (List). Get categories for a company. Returns the list of categories for the company. The user PAT needs to have the scope mx:app:categories:read. [Project Category API: GET /v1/companies/{company-id}/categories. Needs a Personal Access Token.] Required: company_id.
- **Create a Mendix category** (Create). Create a category for a company. Creates a category for the company. The category must include at least 2 inner values. Validation: A company can have a maximum of 5 categories. The user PAT needs to have the scope mx:app:categories:write. The user must be a company admin. The code of the provided values can be passed as an empty string. [Project Category API: POST /v1/companies/{company-id}/categories. Needs a Personal Access Token.] Required: company_id.
- **Update a Mendix category by ID** (Update). Update a category. Updates a category. The user PAT needs to have the scope mx:app:categories:write. The user must be a company admin. [Project Category API: PUT /v1/categories/{category-id}. Needs a Personal Access Token.] The id is the category-id. Required: id.
- **Delete a Mendix category by ID** (Delete). Delete a category. Deletes a category. The user needs to have the scope mx:app:categories:write. The user must be a company admin. [Project Category API: DELETE /v1/categories/{category-id}. Needs a Personal Access Token.] The id is the category-id. Required: id.
- **List all Mendix category values** (List). Get values for a category. Returns the list of values for a category. A maximum of 100 values can be returned per page. The user PAT needs to have the scope mx:app:categories:read. [Project Category API: GET /v1/categories/{category-id}/values. Needs a Personal Access Token.] Required: category_id.
- **Create a Mendix category value** (Create). Add values to a category. Adds values to a category. Validation: A company allows a maximum of 250 values per category. The user PAT needs to have the scope mx:app:categories:write. The user must be a company admin. The code of the provided values can be passed as an empty string. [Project Category API: POST /v1/categories/{category-id}/values. Needs a Personal Access Token.] Required: category_id.
- **Update a Mendix category value by ID** (Update). Update a value of a category. Updates the value of a category. The user PAT needs to have the scope mx:app:categories:write. The user must be a company admin. The code of the provided value can be passed as an empty string. A code will be generated based on the provided input for the values. [Project Category API: PUT /v1/categories/{category-id}/values/{value-id}. Needs a Personal Access Token.] The id is the value-id. Required: id, category_id.
- **Delete a Mendix category value by ID** (Delete). Delete a value of a category. Deletes a value of a category. Validation: At least two values must remain. The user PAT needs to have the scope mx:app:categories:write. The user must be a company admin. [Project Category API: DELETE /v1/categories/{category-id}/values/{value-id}. Needs a Personal Access Token.] The id is the value-id. Required: id, category_id.
- **Create a Mendix certificate replacement** (Create). Replace a certificate. Rotates a certificate: moves all custom domains linked to it onto another certificate you own, without downtime. [Certificate API: PUT /v1/certificates/{certificateId}/replacement. Needs a Personal Access Token.] Required: certificate_id, newCertificateId.
- ...and 125 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
