RELATED 01
trace-mcp
Local code graph of a repository, queried over MCP for impact, call paths and context
202GitHub stars
3.8k/wknpm downloads
62popularity score
BC Code Intelligence MCP Server
Business Central and AL development guidance from a bundled knowledge base of specialist personas
By Jeremy Vyska (individual) TypeScript Local · stdio Developer toolsKnowledge and memory
52 popularity score ★ 95 ↓ 2.0k/wk
Connect your client
Local (npm)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude CodeTerminal
claude mcp add bc-code-intelligence -- npx -y bc-code-intelligence-mcpClaude Desktopclaude_desktop_config.json
{
"mcpServers": {
"bc-code-intelligence": {
"command": "npx",
"args": [
"-y",
"bc-code-intelligence-mcp"
]
}
}
}Cursor~/.cursor/mcp.json
{
"mcpServers": {
"bc-code-intelligence": {
"command": "npx",
"args": [
"-y",
"bc-code-intelligence-mcp"
]
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"bc-code-intelligence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bc-code-intelligence-mcp"
]
}
}
}Codex~/.codex/config.toml
[mcp_servers.bc-code-intelligence]
command = "npx"
args = ["-y", "bc-code-intelligence-mcp"]Gemini CLITerminal
gemini mcp add --scope user bc-code-intelligence npx -- -y bc-code-intelligence-mcpSettings 5
BC_CODE_INTEL_CONFIG_PATH |
Optional: Path to a config file; BCKB_CONFIG_PATH is the legacy name. Otherwise ~/.bc-code-intel/config.json and project files are looked up. |
|---|---|
BC_CODE_INTEL_COMPANY_KNOWLEDGE_URL |
Optional: Git URL of a company knowledge layer to load. |
BC_CODE_INTEL_COMPANY_KNOWLEDGE_TOKEN |
Optional: Token for a private company knowledge repository. |
BC_CODE_INTEL_COMPANY_KNOWLEDGE_BRANCH |
Optional: Branch of the company layer, main by default. |
BC_CODE_INTEL_COMPANY_KNOWLEDGE_AUTH_TYPE |
Optional: az_cli, gh_cli or ssh when no token is given. |
What it does
BC Code Intelligence is a local Node.js server aimed at developers building Microsoft Dynamics 365 Business Central extensions in AL. It ships a knowledge base of topics and a cast of named specialist personas (debugging, upgrades, testing, code review, security, AppSource publishing, DevOps and more) that an assistant can search, quote and hand work between.
Beyond lookups, it can run multi-step workflows (start, advance, batch, cancel), analyse AL code passed to it, and unpack Business Central snapshot (.snap) debug archives into a temporary folder so their trace and AL files can be read. Teams can stack their own content on top of the bundled layer: a project folder, or a company git repository given by URL, with token, Azure CLI, GitHub CLI or SSH sign-in.
The README describes a handful of tools and the install wiki still says 8, but the source at v1.7.6 (src/tools/index.ts) registers 21 tools by default, including file-writing tools for scaffolding new knowledge layers, plus 6 diagnostic tools that only appear when developer.enable_diagnostic_tools is set in its config.
What it needs
| Runtime | Node.js 18+ |
|---|
Node.js 18 or later with npx (the wiki also names npm 8+). An MCP client such as VS Code in Agent Mode, Claude Desktop or Cursor. No Business Central tenant or account is needed. A company knowledge layer needs a git repository reachable by URL and, if private, a token or a signed-in az, gh or SSH setup.
Limits
It serves guidance and stored content; it does not connect to a Business Central environment, compile AL or deploy extensions. The answers come from its bundled and layered knowledge, so quality depends on that content. The Installation Guide wiki is out of date: it lists 8 tools and a clone URL for an older repository name (bc-knowledgebase-mcp). Diagnostic tools are hidden unless enabled in config. A company git layer uses the main branch unless BC_CODE_INTEL_COMPANY_KNOWLEDGE_BRANCH is set.
Who it suits
Suits AL developers working on Business Central extensions who want structured advice, review checklists and upgrade guidance inside their editor, and teams that want to publish their own standards to every developer through a shared git layer. It runs locally and needs no account by default. It is a community project, not from Microsoft. Pick something else if you need an assistant to act on a live Business Central tenant or build and publish apps; this server only advises and manages its own content files.
Tools 27
find_bc_knowledge- Search the knowledge base for Business Central topics
get_bc_topic- Fetch one knowledge topic in full
ask_bc_expert- Route a question to the fitting specialist persona
analyze_al_code- Review AL code for patterns and issues
list_specialists- List the available specialist personas
extract_bc_snapshot- Unpack a .snap debug archive into a temp folder
set_workspace_info- Set the project root and other available MCP servers
get_workspace_info- Show the current workspace settings
workflow_list- List the available guided workflows
workflow_start- Begin a guided workflow
workflow_next- Move a workflow to its next step
workflow_progress- Report progress on a workflow step
workflow_status- Show where a workflow stands
workflow_complete- Finish a workflow
workflow_batch- Process several workflow items at once
workflow_cancel- Abandon a running workflow
get_codelens_mappings- Return code-pattern mappings used by the VS Code extension
validate_layer_repo- Check a knowledge layer folder for structural problems
scaffold_layer_repo- Create a new layer folder structure with templates
create_layer_content- Write a new topic, specialist or prompt file into a layer
list_prompts- List prompts defined in the loaded layers
diagnose_git_layer- Diagnostic: troubleshoot a git-based layer (opt-in)
validate_layer_config- Diagnostic: check the layer configuration (opt-in)
test_azure_devops_pat- Diagnostic: test an Azure DevOps access token (opt-in)
get_layer_diagnostics- Diagnostic: report on loaded layers (opt-in)
diagnose_local_layer- Diagnostic: troubleshoot a local folder layer (opt-in)
reload_layers- Diagnostic: reload all layers without restarting (opt-in)