Highlighting posts and resources from the Business Central development community — May 3–May 9, 2026
A strong week for AL tooling and AI-assisted development. Vjeko ships AL MCP Bridge so any agent — Claude Code, Cursor, Codex — can drive the AL Language Server, and Javi Armesto introduces BCQuality, an open repo of remedial knowledge for AL coding agents. Gerardo Rentería pushes VS Code Agent Hooks onto Copilot, Steven Renders maps each AI assistant to the AL work where it actually pulls its weight, and Amol Salvi previews Clarity AI for decoding cryptic BC error messages.
Recent Posts (May 3–9, 2026)
➡️ 1. The MCP Bridge: AL Language Tools for Every Agent
📇 Author: Vjeko Babić
🗓️ Date: May 3, 2026
🌎 Link: vjeko.com
📝 Summary: The official AL extension for VS Code keeps every coding agent that doesn’t live inside VS Code — Claude Code, Cursor, Codex, you name it — locked out of the AL Language Server. Vjeko’s AL MCP Bridge fixes that by exposing the AL Language Server’s capabilities (diagnostics, symbol lookup, hover, definition, code actions, completions) through MCP so any agent can drive the same tooling Copilot uses. The result is a tight feedback loop in your agent of choice — compile errors, type info, and refactor suggestions stop being string-matched against shipped.appfiles and start coming from the real compiler.
➡️ 2. BCQuality: An Agentic Vision for AL Development
📇 Author: Javi Armesto (also appeared in the April 26–May 2 newsletter)
🗓️ Date: May 3, 2026
🌎 Link: techspheredynamics.com
📝 Summary: Public preview of BCQuality, an open repository of remedial knowledge for AL development agents. Built on an “admission rule” — only include guidance the LLM doesn’t already know — the repo is structured in three layers (Microsoft baseline, community, custom) and ships action skills for code review across performance, security, privacy, upgrade, style, and UI. The initial Microsoft layer includes 99 knowledge files covering things likeSetLoadFieldsordering,FindSet(true)locking semantics, and other patterns where general-purpose models tend to drift.
➡️ 3. VS Code Agent Hooks: Give Copilot Context Before the First Message
📇 Author: Gerardo Rentería
🗓️ Date: May 3, 2026
🌎 Link: gerardorenteria.blog
📝 Summary: VS Code Agent Hooks (SessionStart,PreCompact, and friends) let you run code at well-defined lifecycle points so Copilot has the context it needs before the first user message. Gerardo’s worked example uses an onboarding questionnaire that captures the developer’s experience level (junior / mid / senior) and writes a behavior profile to JSONL — so when the conversation gets compacted, the profile is reloaded on the nextSessionStartand the agent doesn’t lose its tone or constraints. Includes the.github/hooks/folder layout and a PowerShell executor pattern.
➡️ 4. How Do I: Choose the Right AI Assistant for AL Development?
📇 Author: Steven Renders
🗓️ Date: May 4, 2026
🌎 Link: thinkaboutit.be
📝 Summary: Steven compares the AI assistants AL developers reach for and matches each to the work where it pulls its weight: GitHub Copilot for inline completions and codebase-aware edits inside VS Code; Claude.ai / Claude Desktop for architecture and reasoning-heavy questions where you don’t want a model multiplier on every turn; Copilot Agent mode for multi-file refactors where the editor context justifies the cost. Sets up the June 1 usage-based billing change and previews how sub-agent model selection will start showing up on the invoice.
➡️ 5. Meet Clarity AI: The AI Assistant That Explains Your Business Central Errors
📇 Author: Amol Salvi (also appeared in the April 26–May 2 newsletter)
🗓️ Date: May 4, 2026
🌎 Link: bcaihub.com
📝 Summary: Building on last week’s piece on why BC errors are hard to decode, Amol previews Clarity AI — an assistant that takes a raw BC error message, correlates it with telemetry, source AL, and recent code changes, and returns a plain-language root cause and a candidate fix. The post sketches the workflow (paste the error, get the explanation, drill into the offending event subscriber or table extension) and frames it as the “first responder” tier between user-facing error text and a developer opening the debugger.
Community Resources
Official Resources
GitHub Repositories
- microsoft/BCApps – Repository for collaboration on Microsoft Dynamics 365 Business Central applications.
- microsoft/BCTech – Business Central technology samples.
- microsoft/ALAppExtensions – Repository for collaboration on Microsoft AL application add-on and localization extensions for Microsoft Dynamics 365 Business Central.
- microsoft/AL – Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code.
- StefanMaron/MSDyn365BC.Code.History – Contains the Microsoft Business Central Code. Updated each month.
Follow on Social Media
- Twitter/X Hashtags: #MSDyn365BC | #BusinessCentral
Stay Connected
The Business Central AL development community stays active with valuable content on AL development, upgrades, integrations, and tooling improvements. Following #MSDyn365BC and #BusinessCentral on Twitter/X is a great way to catch new posts as they’re published.
Note: This review is compiled from publicly available blog posts and community resources. Links to external blog posts are provided for your information only and do not constitute endorsement or validation of their content. Publication information and availability are subject to change. Always verify information against official documentation for production use.