Delphi Build MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DELPHI_CONFIG | Yes | Path to the delphi_config.toml configuration file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compile_delphi_projectA | Compile a Delphi project (.dpr or .dproj file) and return parsed results. For Windows targets (Win32/Win64/Win64x), uses MSBuild for IDE-identical output including icons, manifests, and DPI awareness. For cross-compilation targets (Linux64/Android/Android64), uses direct dcc compiler invocation. Returns only compilation errors, filtering out warnings and hints. |
| generate_config_from_build_logA | Generate delphi_config.toml file automatically by parsing an IDE build log. For Windows targets, generates a minimal config with only the Delphi installation path (MSBuild handles all other settings). For cross-compilation targets (Linux64/Android), generates a full config with all library paths and compiler settings. |
| generate_config_from_multiple_build_logsA | Generate delphi_config.toml file from multiple IDE build logs for different configurations and platforms. By default, creates separate platform-specific config files (e.g., delphi_config_win32.toml, delphi_config_win64.toml). Use this when you have build logs from multiple configurations (Debug/Release) and/or platforms (Win32/Win64/Linux64/Android/Android64). |
| extend_config_from_build_logA | Extend an existing delphi_config.toml with settings from a new IDE build log. Useful for adding support for new platforms (e.g., Win64x) or libraries without regenerating the entire configuration. Intelligently merges new paths while preserving existing settings and avoiding duplicates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: compile a project, generate a config from a single build log, generate configs from multiple build logs, and extend an existing config. The descriptions clearly separate these cases, so an agent should rarely confuse them.
All tool names use consistent snake_case and follow a clear verb-object pattern. The config tools share the 'config_from_build_log' suffix, which makes their relationship and differences immediately obvious.
Four tools is well-scoped for a Delphi build server: one compilation tool and three config-generation variants. Each tool serves a distinct, non-redundant purpose in the workflow.
The core workflow of compiling and generating/ extending configuration from build logs is covered. There is no tool to inspect or validate the generated config, but that is an ancillary gap rather than a workflow dead end.