bc-code-intelligence-mcp
by JeremyVyska
README.md
# BC Code Intelligence MCP Server
[](https://vscode.dev/redirect/mcp/install?name=bc-code-intel&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22bc-code-intelligence-mcp%22%5D%7D)
[](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide)
**Get instant help from AI Business Central experts** right in your favorite AI tool. No more searching docs - just ask and get expert guidance tailored to your specific BC development challenges.
---
## π Quick Start
1. **Click the blue "Install with NPX" button above** (VS Code users)
2. **Switch to Agent Mode** in VS Code's Copilot Chat
3. **Just ask!** - Start with any prompt below
> **Other platforms?** See the [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) for Claude Desktop, Cursor, and more.
---
## π€ New to AI-Assisted Development? Start with Parker
If you're not sure how to work with AI tools, or you're skeptical about letting AI touch your codeβ**that's exactly why Parker exists**.
Parker is a grizzled veteran who helps you work WITH AI safely:
- Creates **reviewable proposals** instead of making direct changes
- **Explains AI reasoning** so you understand what's happening and why
- **Coordinates other specialists** to validate suggestions before you commit
- Builds trust **gradually** through transparency and verification
**Just say:**
- "Parker, I'm new to AI development tools. Help me understand how this works."
- "Parker, I don't trust AI to write my code. What's a safe way to start?"
- "Parker, review what the AI just suggested before I accept it."
Once you're comfortable, you can work directly with any specialistβbut Parker's always there when you want that extra layer of verification and explanation.
---
## π¬ Just Ask - Example Prompts
The BC Code Intelligence specialists are ready to help. Just type naturally - here are some examples:
### π Debugging & Performance (Dean)
- "Dean, help me debug this error: 'The record in table Customer already exists'"
- "I'm seeing slow performance when posting sales orders. Can Dean take a look?"
- "Ask Dean why my FlowField is always showing zero"
### ποΈ Legacy Code & Upgrades (Logan)
- "Logan, I need to upgrade my extension from BC v24 to v27"
- "I inherited this old extension - can Logan help me understand what it does?"
- "Help me modernize this C/AL-style code to proper AL patterns"
### π Version Migration & Breaking Changes (Victor)
- "Victor, help me upgrade from BC25 to BC26"
- "I'm seeing obsolete warnings after upgrading - what do I need to change?"
- "What breaking changes should I know about in BC27?"
- "Help me resolve this compile error after a runtime upgrade"
### π§ DevOps & CI/CD (Lena)
- "Lena, help me set up AL-Go for my BC extension"
- "I need to configure an Azure DevOps pipeline with ALOps"
- "How do I use BCContainerHelper for local BC development?"
- "Help me integrate Cosmo Alpaca for automated testing"
### ποΈ Architecture & Design (Alex)
- "Alex, review my extension's architecture before I submit to AppSource"
- "I need to design an integration with an external warehouse system"
- "What's the best way to structure a multi-company solution?"
### π» Coding & Implementation (Sam)
- "Sam, help me write a function to calculate weighted average cost"
- "I need to create a FactBox that shows related sales history"
- "Show me the best way to implement a posting routine"
### π§ͺ Testing & Quality (Quinn)
- "Quinn, help me create test coverage for my posting codeunit"
- "What test scenarios should I include for this validation?"
- "Review my test codeunit for completeness"
### π Code Review (Roger)
- "Roger, review this codeunit for best practices"
- "Check if my code follows BC naming conventions"
- "Are there any code smells in my Customer Card extension?"
### π Security (Seth)
- "Seth, review my permission sets for security issues"
- "How should I handle user permissions for this sensitive data?"
- "Check if my API is exposing too much information"
### π Integration & Events (Jordan)
- "Jordan, help me design an event-driven integration"
- "What's the best way to subscribe to posting events?"
- "How do I create a clean API for external systems?"
### β οΈ Error Handling (Eva)
- "Eva, help me implement proper error handling for this process"
- "What's the best way to validate user input before posting?"
- "Review my Try/Catch implementation"
### π¨ User Experience (Uma)
- "Uma, help me improve my page layout for better usability"
- "Can we switch from simple Error calls in this app to ErrorInfo with suggested actions?"
- "Review my action menu structure"
### πͺ AppSource & ISV (Morgan)
- "Morgan, help me prepare my app for AppSource submission"
- "What are the common AppSource validation failures?"
- "Review my app's technical baseline for AppSource"
### π©βπ« Learning & Mentoring (Maya)
- "Maya, explain how dimensions work in BC"
- "I'm new to AL - help me understand events and subscribers"
- "Walk me through how posting routines work"
### π Documentation (Taylor)
- "Taylor, help me document this complex codeunit"
- "Generate XML documentation for my public procedures"
- "Review my app's README for completeness"
---
## π₯ Meet Your BC Specialist Team
| Specialist | Expertise | Best For |
|------------|-----------|----------|
| **π€ Parker** | AI Trust & Transparency | New to AI tools, safe collaboration, verification-first |
| **ποΈ Alex** | Architecture & Design | Solution design, extension structure, integration patterns |
| **π» Sam** | Expert Coder | Writing AL code, implementation patterns, coding questions |
| **π Dean** | Debugging & Performance | Errors, slow queries, troubleshooting |
| **β οΈ Eva** | Error Handling | Validation, Try/Catch, error messages |
| **π§ͺ Quinn** | Testing | Test codeunits, test scenarios, code coverage |
| **π Roger** | Code Review | Best practices, naming conventions, code quality |
| **π Seth** | Security | Permissions, data protection, API security |
| **π Jordan** | Integration | APIs, events, external connections |
| **ποΈ Logan** | Legacy & Upgrades | Version migrations, old code, modernization |
| **π Victor** | Version Migration | BC upgrades, breaking changes, deprecations |
| **π§ Lena** | DevOps & CI/CD | AL-Go, ALOps, BCContainerHelper, pipelines |
| **π¨ Uma** | User Experience | Page design, usability, UI patterns |
| **πͺ Morgan** | AppSource & ISV | Publishing, validation, business concerns |
| **π©βπ« Maya** | Mentoring | Learning concepts, explanations, training |
| **π Taylor** | Documentation | Code docs, READMEs, knowledge sharing |
| **βοΈ Chris** | MCP Configuration | Company/Project MCP knowledge layer help |
---
## π Learn More
| Topic | Link |
|-------|------|
| **Full Installation Options** | [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) |
| **Common Scenarios** | [Usage Patterns](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Common-Scenarios) |
| **All MCP Tools** | [Tools Reference](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/MCP-Tools-Reference) |
| **Company Standards** | [Enterprise Configuration](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Enterprise-Configuration) |
| **Structured Workflows** | [Methodology Framework](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Methodology-Framework) |
| **Troubleshooting** | [Common Issues](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Troubleshooting) |
---
## π‘ Tips
- **Just use first names** - "Ask Dean" works just as well as "Ask Dean Debug"
- **Be specific** - Include error messages, code snippets, or version numbers when relevant
- **Specialists collaborate** - They'll hand off to each other when needed
- **Context carries over** - Continue conversations naturally
---
## π€ Contributing
See the [Contributing Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Contributing-Guide) for how to contribute to this project.
## π License
MIT License - see [LICENSE](LICENSE) for details.
TDQS
A4/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct action or resource: workspace management, knowledge browsing, workflow control, etc. Overlaps are minimal and clarified by descriptions.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case, with workflow_ prefix for workflow tools. No mixing of conventions.
Tool Count5/5
21 tools are well-scoped across multiple subsystems (workspace, knowledge, workflows, analysis) with no redundancy. Each tool serves a clear purpose.
Completeness5/5
The tool surface covers the full lifecycle: workspace setup, knowledge retrieval, layer management, workflow orchestration, and code analysis. No obvious missing operations.
Maintenance
ActivityInactive
ResponsivenessUnresponsive