ALCops MCP Server
ALCops/mcp-server
Análise de código Business Central AL integrada a assistentes de IA via MCP
Ver no GitHubServidor MCP que integra os analisadores de código AL (Business Central) do ALCops a assistentes de IA como Claude e Cursor. Permite analisar projetos AL, consultar regras de linting e aplicar correções de código diretamente na conversa, sem sair do assistente.
Instalação
npx convez-ai ALCops/mcp-server1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Analisar projetos AL do Business Central em tempo real dentro do Claude
- Consultar e navegar regras de 6 cops (ApplicationCop, DocumentationCop, FormattingCop, etc)
- Obter e aplicar correções automáticas de código para diagnosticados AL
Veredito

Excelente para desenvolvedores Business Central que usam Claude ou Cursor. Integração robusta via MCP com suporte a analyzers nativos e third-party, e ferramentas bem projetadas (analyze, list_rules, get_fixes, apply_fix). Requer .NET 10 e AL Language v17+.
README
A tradução para o português deste README ainda está na fila.
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
4 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 and return the modified source — does not write to disk. |
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:
BCDEVELOPMENTTOOLSPATHenvironment variable- AL Language VS Code extension
- Local cache (
~/.alcops/cache/devtools/) - .NET global tools cache
- 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.