Dynamics 365 Business Central: using AL MCP Server from GitHub Copilot CLI.
The AL MCP Server exposes AL development tools through the Model Context Protocol, allowing CLI-based AI agents to perform AL operations like building, compiling, and publishing without Visual Studio Code. Install via dotnet tool and configure in GitHub Copilot CLI to automate AL development workflows in CI/CD pipelines and agent-driven scenarios.
post Stefano Demiliani
"It runs as a separate process and doesn't require Visual Studio Code."
Key points
- AL MCP Server runs as a standalone process that exposes AL development tools over the Model Context Protocol for any MCP-compatible AI agent
- Install via dotnet tool command: dotnet tool install –global microsoft.dynamics.businesscentral.development.tools –prerelease
- Configure in GitHub Copilot CLI by adding MCP server with name, selecting STDIO type, and entering command: al launchmcpserver
- Enables automated workflows where agents call AL tools in sequence like al_downloadsymbols, al_compile, and al_getdiagnostics for CI/CD validation
- Supports AppSource validation by running code analysis with AppSourceCop and filtering diagnostics by specific areas
Quotes
- “It runs as a separate process and doesn’t require Visual Studio Code.” (Highlights the key advantage for CI/CD pipelines and headless automation scenarios)
Context
- Features: AL MCP Server, Model Context Protocol integration, Symbol download, Code compilation, Publishing extensions, Diagnostics, Code analysis, AppSource validation
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.