Other AI tools
Claude Code is the default integration, but mxcli also supports OpenCode, Cursor, Continue.dev, Windsurf, Aider, and Mistral Vibe. Each tool gets its own configuration file that teaches the AI about MDL syntax and mxcli commands.
Initializing for a specific tool
Use the --tool flag to specify which AI tool you use:
# OpenCode
mxcli init --tool opencode /path/to/my-mendix-project
# Cursor
mxcli init --tool cursor /path/to/my-mendix-project
# Continue.dev
mxcli init --tool continue /path/to/my-mendix-project
# Windsurf
mxcli init --tool windsurf /path/to/my-mendix-project
# Aider
mxcli init --tool aider /path/to/my-mendix-project
# Mistral Vibe
mxcli init --tool vibe /path/to/my-mendix-project
Setting up multiple tools
You can configure several tools at once. This is useful if different team members use different editors, or if you want to try several tools on the same project:
# Multiple tools
mxcli init --tool claude --tool cursor /path/to/my-mendix-project
# All supported tools at once
mxcli init --all-tools /path/to/my-mendix-project
Adding a tool to an existing project
If you already ran mxcli init and want to add support for another tool without re-initializing:
mxcli add-tool cursor
mxcli add-tool windsurf
This creates the tool-specific config file without touching the existing setup.
What each tool gets
Every tool gets the universal files that are always created:
| File | Purpose |
|---|---|
AGENTS.md | Comprehensive AI assistant guide (works with any tool) |
.ai-context/skills/ | MDL pattern guides shared by all tools |
.ai-context/examples/ | Example MDL scripts |
.devcontainer/ | Dev container configuration |
mxcli | CLI binary |
On top of the universal files, each tool gets its own configuration:
| Tool | Config File | Contents |
|---|---|---|
| Claude Code | .claude/, CLAUDE.md | Settings, skills, commands, lint rules, project context |
| OpenCode | .opencode/, opencode.json | Skills, commands, lint rules, project context |
| GitHub Copilot | .github/copilot-instructions.md, AGENTS.md | Project-level instructions auto-loaded by Copilot in VS Code |
| Cursor | .cursorrules | Compact MDL reference and mxcli command guide |
| Continue.dev | .continue/config.json | Custom commands and slash commands |
| Windsurf | .windsurfrules | MDL rules for Codeium’s AI |
| Aider | .aider.conf.yml | YAML configuration for Aider |
| Mistral Vibe | .vibe/ | Config, system prompt, and SKILL.md skills |
Tool details
OpenCode
OpenCode receives full integration on par with Claude Code: dedicated skills in .opencode/skills/, slash commands in .opencode/commands/, and Starlark lint rules in .claude/lint-rules/. See the dedicated OpenCode Integration page for the complete walkthrough.
mxcli init --tool opencode /path/to/project
GitHub Copilot
GitHub Copilot has dedicated support via --tool copilot, which generates .github/copilot-instructions.md — Copilot’s project-level instructions file that’s automatically loaded in VS Code.
mxcli init --tool copilot /path/to/project
The generated file is compact (Copilot has a smaller instruction context window than Claude Code) and points to AGENTS.md and .ai-context/skills/ for full reference material. It includes the critical ./mxcli (not mxcli) rule, quick command examples, and MDL syntax reminders.
For many organizations, Copilot is the default AI assistant as part of their Microsoft/GitHub enterprise agreement. To use: open the project in VS Code with the GitHub Copilot extension, open Copilot Chat (Ctrl+Shift+I), and ask for Mendix changes. Copilot will reference .github/copilot-instructions.md, AGENTS.md, and the skill files for MDL syntax guidance.
Cursor
Cursor reads its instructions from .cursorrules in the project root. The file mxcli generates contains a compact MDL syntax reference and a list of mxcli commands the AI can use. Cursor’s Composer and Chat features will reference this file automatically.
mxcli init --tool cursor /path/to/project
Created files:
.cursorrules– MDL syntax, command reference, and conventionsAGENTS.md– universal guide (Cursor also reads this).ai-context/skills/– shared skill files
To use: open the project in Cursor, then use Composer (Ctrl+I) or Chat (Ctrl+L) to ask for Mendix changes.
Continue.dev
Continue.dev uses a JSON configuration file with custom commands. The generated config tells Continue about mxcli and provides slash commands for common MDL operations.
mxcli init --tool continue /path/to/project
Created files:
.continue/config.json– custom commands, slash command definitionsAGENTS.mdand.ai-context/skills/– universal files
To use: open the project in VS Code with the Continue extension, then use the Continue sidebar to ask for changes.
Windsurf
Windsurf reads .windsurfrules from the project root. The generated file contains MDL rules and mxcli command documentation tailored for Codeium’s AI.
mxcli init --tool windsurf /path/to/project
Created files:
.windsurfrules– MDL rules and command referenceAGENTS.mdand.ai-context/skills/– universal files
To use: open the project in Windsurf, then use Cascade to ask for Mendix changes.
Aider
Aider is a terminal-based AI pair programming tool. The generated YAML config tells Aider about the project structure and available commands.
mxcli init --tool aider /path/to/project
Created files:
.aider.conf.yml– Aider configurationAGENTS.mdand.ai-context/skills/– universal files
To use: run aider in the project directory from the terminal.
Mistral Vibe
Mistral Vibe is a terminal-based AI coding agent by Mistral AI. It uses .vibe/config.toml for configuration, .vibe/prompts/ for system prompts, and .vibe/skills/ for SKILL.md-based skills.
mxcli init --tool vibe /path/to/project
Created files:
.vibe/config.toml– project configuration with system prompt reference.vibe/prompts/mendix-mdl.md– system prompt with project context and mxcli commands.vibe/skills/write-microflows/SKILL.md– microflow syntax and rules.vibe/skills/create-page/SKILL.md– page/widget syntax.vibe/skills/check-syntax/SKILL.md– validation workflow.vibe/skills/explore-project/SKILL.md– project query commandsAGENTS.mdand.ai-context/skills/– universal files
To use: run vibe in the project directory from the terminal. Vibe auto-discovers skills in .vibe/skills/ and loads the system prompt from .vibe/prompts/.
The universal format: AGENTS.md
Regardless of which tool you pick, mxcli always creates AGENTS.md and the .ai-context/ directory. These use a universal format that most AI tools understand:
AGENTS.mdis a comprehensive guide placed in the project root. It describes mxcli, lists MDL commands, and explains the development workflow. Many AI tools (GitHub Copilot, OpenAI Codex, and others) automatically read markdown files in the project root..ai-context/skills/contains the same skill files that Claude Code gets, but in the shared location. Any tool that can read project files can reference these.
This means even if your AI tool is not in the supported list, it can still benefit from mxcli init. The AGENTS.md file and skill directory provide enough context for any AI assistant to work with MDL.
Listing supported tools
To see all tools mxcli knows about:
mxcli init --list-tools
Next steps
To understand what the skill files contain and how they guide AI behavior, see Skills and CLAUDE.md.