AL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| al_search_objectsA | Search AL objects in YOUR WORKSPACE (.app packages). Analyzes compiled AL code structure. Use summaryMode:true & limit for token efficiency. For complex objects prefer al_get_object_summary. Supports domain filtering. |
| al_get_object_definitionB | Get AL object definition from YOUR WORKSPACE. Retrieves compiled code structure by ID or name. Use summaryMode:true for token efficiency. Use limits for large objects. |
| al_find_referencesB | Find object/field references in YOUR WORKSPACE. Tracks extensions, variables, parameters, field usage, and table relations across all object types. |
| al_search_object_membersA | Search procedures, fields, controls, or dataitems within an object in YOUR WORKSPACE. Unified search for all object child elements. |
| al_get_object_summaryA | ✅ TOKEN EFFICIENT: Get categorized overview of AL object in YOUR WORKSPACE. Intelligent procedure grouping with 96% token reduction vs full definition. |
| al_packagesB | Package management: load compiled .app packages, list loaded packages, or get stats. Auto-discovers .alpackages if path provided. |
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 6 tools
Each tool has a clearly distinct purpose: references, object definition, summary, package management, member search, and object search. No overlap; an agent can easily differentiate.
Five tools follow the 'al_verb_noun' pattern (e.g., al_find_references, al_get_object_definition), but 'al_packages' uses a noun only, breaking the pattern. Otherwise consistent.
With 6 tools, the set is well-scoped for AL development code analysis. Each tool serves a distinct purpose without being excessive or insufficient.
Covers core code analysis needs: references, definitions, summaries, and searches. Missing modification or deployment tools, but read-only analysis is reasonably complete.