Delphi Build MCP Server

A Model Context Protocol (MCP) server that enables AI coding agents like Claude Code to compile Delphi projects programmatically.

Features

• IDE-Identical Windows Builds: Windows targets (Win32/Win64/Win64x) compile via MSBuild, producing byte-identical output to the Delphi IDE — including icons, manifests, and DPI awareness
• Hybrid Compilation: MSBuild for Windows targets, direct dcc for cross-compilation (Linux64/Android/Android64)
• Minimal Configuration: Windows targets need only the Delphi installation path — MSBuild reads everything else from the .dproj
• Automatic Configuration: Generate config from IDE build logs with multi-line parsing
• Multi-Config Support: Generate unified config from multiple build logs (Debug/Release × Win32/Win64/Win64x/Linux64)
• Extend Configuration: Add new platforms or libraries to existing config without regenerating
• Smart Compilation: Reads .dproj files for build settings and compiler flags
• Package Support: Compiles both application (.dpr) and package (.dpk) projects with correct output (.exe/.bpl)
• Filtered Output: Returns only errors, filters out warnings and hints
• Multi-Language Support: Parses both English and German compiler output
• Response File Support: Handles command lines >8000 characters automatically
• Cross-Platform: Supports Win32, Win64, Win64x (LLVM), Linux64, Android, and Android64
• Environment Variables: Auto-expands ${USERNAME} in paths
• MCP Compatible: Works with Claude Code, Cline, and other MCP clients
• Network Transport: Streamable HTTP support for remote access (e.g., WSL-Ubuntu to Windows host)
• WSL Interop: Use from WSL-Ubuntu via stdio through Windows Python or via Streamable HTTP

Quick Start

1. Install

# Install UV if you haven't already
# Windows: powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
# Or: pip install uv

cd delphi-build-mcp-server
uv venv
uv pip install -e .

2. Generate Configuration

In Delphi IDE:

1. Tools > Options > Building > Show compiler progress > "Verbose"
2. Build your project
3. View > Messages > Right-click > Copy All
4. Save to build.log

Then generate config:

Single Build Log (simple projects):

# Platform-specific config is generated by default (e.g., delphi_config_win64.toml)
uv run python -m src.config_generator build.log

# Generate generic delphi_config.toml instead
uv run python -m src.config_generator build.log --generic

Multiple Build Logs (multi-platform projects):

For projects targeting multiple platforms (Win32/Win64/Linux64), create build logs for each configuration:

1. Build in IDE with each Platform/Config combination
2. Save each build log separately (e.g., build_debug_win32.log, build_release_linux64.log)
3. Generate config from all logs:

# Separate platform-specific config files (default)
uv run python -m src.multi_config_generator build_win32.log build_win64.log
# Creates: delphi_config_win32.toml, delphi_config_win64.toml

# Custom output directory for platform-specific files
uv run python -m src.multi_config_generator *.log -d ./configs/

# Single unified config instead of separate files
uv run python -m src.multi_config_generator build_win32.log build_win64.log --unified -o my_config.toml

# Disable environment variable substitution
uv run python -m src.multi_config_generator *.log --no-env-vars

Configuration Strategy:

Windows targets (Win32/Win64/Win64x) use MSBuild, which reads all compiler settings from the .dproj file. Only a minimal delphi_config.toml with the Delphi installation path is needed. Cross-compilation targets (Linux64/Android/Android64) still need full platform-specific config files.

| Platform | Config File | Content | |----------|-------------|---------| | Win32/Win64/Win64x | delphi_config.toml | Minimal (only [delphi] section) | | Li

... View full README on GitHub