ALCops MCP Server

An MCP server that brings ALCops AL code analysis to AI assistants. Lets Claude, Cursor, and other MCP clients analyze Business Central AL projects, browse rules, and apply code fixes — all without leaving the conversation.

Quick Start

Install as a .NET global tool:

dotnet tool install -g ALCops.Mcp

Add to your .mcp.json (Claude Code) or claude_desktop_config.json (Claude Desktop):

{
  "mcpServers": {
    "alcops": {
      "command": "alcops-mcp"
    }
  }
}

That's it. If you have the AL Language VS Code extension installed, the server picks up the BC Development Tools automatically.

Requirements

• .NET 10.0 SDK or Runtime
• AL Language VS Code extension v17.0 or higher

Note: AL Language v16 and earlier are not supported. The BC Development Tools DLLs introduced breaking API changes in v17 that are not backwards compatible. AL Language v18+ requires .NET 10.

Tools

5 tools, ~1,020 tokens of schema overhead.

| Tool | Description | |------|-------------| | analyze | Run analyzers on an AL project or file. Returns diagnostics with severity, location, and code fix availability. | | list_rules | List all available analyzer rules with metadata (ID, title, severity, category, cop). | | get_fixes | Get available code fixes for a specific diagnostic at a location. | | apply_fix | Apply a code fix to resolve a diagnostic. Writes the fixed content directly to the file on disk. | | apply_fix_all | Apply a code fix to every occurrence of a diagnostic rule across a project or a single file (like VS Code's "Fix all in workspace"). Writes to disk unless dryRun is set. |

Analyzers

The server always includes ALCops' 6 built-in cops:

| Cop | Prefix | Description | |-----|--------|-------------| | ApplicationCop | AC | Correct modeling and behavior of BC objects | | DocumentationCop | DC | Documentation quality and completeness | | FormattingCop | FC | Stylistic and syntactic consistency | | LinterCop | LC | Code smells, maintainability, best practices | | PlatformCop | PC | AL language and runtime semantic correctness | | TestCop | TC | Test codeunit structure and correctness |

Additionally, the server can load BC standard analyzers (${CodeCop}, ${UICop}, ${PerTenantExtensionCop}, ${AppSourceCop}) and third-party analyzers — auto-discovered from al.codeAnalyzers in .vscode/settings.json, or passed explicitly via the analyzers tool parameter.

Browse the complete rules reference at alcops.dev/docs/analyzers.

BC DevTools Resolution

The server needs Microsoft BC Development Tools at runtime (not bundled due to licensing). On startup it searches, in order:

1. BCDEVELOPMENTTOOLSPATH environment variable
2. AL Language VS Code extension
3. Local cache (~/.alcops/cache/devtools/)
4. .NET global tools cache
5. Auto-download from NuGet (first run only)

Most users have the AL extension installed, so no extra setup is needed.

Contributing

Contributions are welcome! Whether it's a new tool, a bug report, or a pull request — all input helps.

• 🐛 Report a bug — File an Issue
• 🔧 Submit a PR — Fork the repo, create a branch, and open a pull request

License

This project is licensed under the MIT License.