OneTech MCP Server
Extract and document Mendix Studio Pro modules via Model Context Protocol (MCP)
OneTech MCP Server enables AI assistants like GitHub Copilot to interrogate local Mendix .mpr files and extract comprehensive module documentation including domain models, pages, microflows, and enumerations.
๐ Quick Start
Install Globally (Recommended)
npm install -g @jordnlvr/onetech-mcp-server
Or Use with NPX (No Install)
npx @jordnlvr/onetech-mcp-server
Configure in VS Code
Add to your VS Code settings.json:
{
"github.copilot.chat.mcp.enabled": true,
"github.copilot.chat.mcp.servers": {
"onetech": {
"command": "npx",
"args": ["@jordnlvr/onetech-mcp-server"]
}
}
}
Or use global install:
{
"github.copilot.chat.mcp.enabled": true,
"github.copilot.chat.mcp.servers": {
"onetech": {
"command": "onetech-mcp-server"
}
}
}
๐ Usage
Once configured, use GitHub Copilot to extract module documentation:
You: "Extract the RequestHub module from D:\Projects\OneTech.mpr"
Copilot: [Uses onetech_extract_module tool]
โ
Successfully extracted 4 files from module 'RequestHub':
- DomainModel.json (57KB)
- Pages.json (42KB)
- Microflows.json (0KB)
- Enumerations.json (4KB)
๐ ๏ธ Available Tools
onetech_extract_module
Extracts domain model, pages, microflows, and enumerations from a Mendix module using mx.exe.
Parameters:
mprPath(required): Absolute path to the.mprfilemoduleName(required): Name of the module to extractoutputPath(required): Absolute path to output directory for JSON filesmxPath(optional): Path tomx.exe(default:D:\Program Files\Mendix\11.3.0.80734\modeler\mx.exe)
Returns:
- JSON files containing complete module structure
- File sizes and extraction status
- Success/error messages
๐ Requirements
- Node.js: >= 18.0.0
- Mendix Studio Pro: Version 11.3.0 or compatible
- mx.exe: Command-line tool (included with Studio Pro)
๐ Privacy & Security
- 100% Local: All processing happens on your machine
- No Cloud: Your
.mprfiles never leave your computer - No Tracking: No telemetry, analytics, or data collection
- Open Source: Full transparency, audit the code yourself
๐ฏ Use Cases
- Documentation Generation: Extract module structure for AI-powered docs
- Code Review: Analyze domain models and microflows
- Migration Planning: Understand module dependencies
- Teaching: Demonstrate Mendix architecture to students
- Onboarding: Help new developers understand existing apps
๐ฆ What Gets Extracted
For each module, the tool generates 4 JSON files:
- DomainModel.json: Entities, attributes, associations, validation rules
- Pages.json: Page layouts, widgets, data sources
- Microflows.json: Logic flows, actions, parameters
- Enumerations.json: Enumeration types and values
๐๏ธ Architecture
Your Machine
โโโ VS Code + GitHub Copilot
โโโ OneTech MCP Server (this package)
โ โโโ Calls mx.exe with your .mpr file
โโโ mx.exe (Mendix CLI)
โโโ Your .mpr files (local, never uploaded)
๐ค Contributing
Built by the OneTech Team for the Mendix developer community.
Found a bug? Open an issue on GitHub. Have a feature request? Let us know!
๐ License
MIT License - See LICENSE file for details
๐ Links
Version: 0.1.0 Status: MVP Release First Mendix MCP Server ๐