AL-Dependency

The AL Dependency MCP Server exposes your AL workspace's compiled symbols (.app files) to AI assistants through the Model Context Protocol (MCP). It analyzes the .al packages found in your project and provides token-optimized, semantics-aware access to objects, references, and package metadata. With this server, AI tools can search for AL objects, inspect object definitions, locate references, inspect object members, and generate concise summaries, all while staying aligned with the actual AL packages you have compiled in your workspace.

Available MCP tools include: al_search_objects to find AL objects by name, type, or patterns; al_get_object_definition to retrieve detailed information about a specific object; al_find_references to locate where objects and fields are used across packages; al_search_object_members to explore child elements like fields, procedures, or dataitems; al_get_object_summary to get a high-level, token-efficient overview; and al_packages to manage and inspect loaded packages. These tools enable precise, context-aware assistance from AI copilots, code review tools, and other MCP-compatible interfaces while avoiding reliance on source code alone.

Prerequisites:

• Node.js 18+ installed on your system
• .NET SDK 8.0+ installed (required for AL tooling and compatibility checks)
• Compiled AL packages (.app files) placed in a .alpackages directory within your workspace

Step-by-step installation:

1. Verify prerequisites:
   • node --version (should be v18+)
   • dotnet --version (should be 8.0+)
2. Ensure your AL apps are compiled and placed in the .alpackages directory at the root of your project.
3. Install and run the MCP server via npx (auto-install is supported):
   • npx al-mcp-server
4. Connect your AI assistant or IDE integrations using the standard MCP connection details:
   • Command: npx
   • Args: ["al-mcp-server"]
   • Type: stdio
5. Optional: add to your editor/IDE configuration as shown in the Quick Start examples (Claude, Copilot, Cursor IDE, Continue, Cody) to automatically invoke the MCP server when needed.

Example command (runs from project root):

npx al-mcp-server

Once running, the server will expose APIs for querying and exploring your AL dependencies via MCP-compatible tools.

Tips and notes:

• The server auto-discovers a .alpackages directory; ensure your compiled .app files are present there before starting.
• If you encounter AL CLI/tooling errors, the server can auto-install necessary AL tools when possible, but you still need a valid .NET SDK 8.0+ environment.
• Common MCP connection issues usually involve misconfigured command/arguments in your tool’s mcp.json or settings. Ensure you reference the correct command (npx) and argument (al-mcp-server).
• Environment variables you may consider configuring (placeholders):
  • MCP_LOG_LEVEL: one of debug, info, warn, error
  • AL_PACKAGES_PATH: path to your .alpackages directory (default: .alpackages at project root)
  • MCP_HOST/ MCP_PORT: to expose the MCP endpoint if your environment requires networking (default behavior uses stdio with the host tooling)
• The server supports multiple MCP-compatible tools; check your AI assistant’s compatibility and adjust the server connection accordingly.
• If you see a MissingPackage or NuGet-related error, verify that your NuGet sources include nuget.org and that the .app packages are compatible with your .NET SDK.