docs: rewrite the MCP Server page for v0.1.0

[Arthurvdv]

Summary

The MCP Server page still described the pre-release alphas: an analyze tool that no longer exists, apply_fix "not writing to disk", six bundled analyzers, and a five-step DevTools resolution list including an auto-download that was removed. ALCops MCP v0.1.0 turned the server into a thin code-fix server that also proxies Microsoft's almcp, and it requires BC Development Tools 18.0+.

This rewrites content/docs/getting-started/ai-tooling.md as a concise install → connect → use guide and fixes the three one-liners elsewhere on the site that repeated the old "analyze a file" story.

What the page now covers

• Prerequisites — .NET 10; BC Development Tools 18.0+, led by dotnet tool install -g Microsoft.Dynamics.BusinessCentral.Development.Tools, with the AL Language VS Code extension as the auto-detected alternative; v17 and earlier not supported.
• Install — dotnet tool install -g ALCops.Mcp.
• Connect your assistant — ready-to-paste configs in a Docsy tabpane for Claude Code, VS Code / GitHub Copilot (servers key, not mcpServers), Cursor and OpenAI Codex; shapes verified against each vendor's current docs.
• What the assistant gets — table of the four native tools (list_rules, get_fixes, apply_fix, apply_fix_all) and a paragraph on the proxied al_* tools, linking to the README for the full list; --no-proxy for clients that already register almcp.
• Analyzers — nothing is bundled; al.codeAnalyzers / al.ruleSetPath / al.packageCachePath come from the project and are bridged to almcp; links to the VS Code page for the analyzer list and the Configuration page for rulesets.
• Recommended agent workflow — a copy-pasteable AGENTS.md / CLAUDE.md loop (compile → get_fixes → apply_fix) plus a warning that al_compile defaults to onlyErrors: true.

Removed: the analyze tool table, the "always includes ALCops' six built-in analyzers" paragraph, the stale resolution list, and the "Other AI Integrations — Under Investigation" alert.

Cross-reference fixes

• content/_index.md — home page "AI assistants" feature card
• content/docs/getting-started/_index.md — AI Tooling bullet
• content/docs/getting-started/quick-start.md — "Ready to Set Up?" bullet

content/docs/_index.md ("connect it to AI assistants through the MCP server") is still accurate and untouched.

Verification

• hugo --gc --minify --panicOnWarning --printPathWarnings (Hugo 0.165.0 extended, as CI) — clean
• markdownlint-cli2@0.23.2 "content/**/*.md" — 0 issues
• htmltest — 0 errors; both new deep links (../vscode/#manual-setup-without-the-extension, ../configuration/#ruleset-files-rulesetjson) resolve
• Rendered page checked from hugo server: four tab headers, warning alert, tools table and every code block present
• claude mcp add --scope project alcops -- alcops-mcp in a scratch folder writes the .mcp.json shown on the page
• No remaining reference to an analyze tool on the touched pages

🤖 Generated with Claude Code