BC Code Intelligence MCP Server - Complete Specialist Bundle with AI-driven expert consultation, seamless handoffs, and context-preserving workflows
npm install bc-code-intelligence-mcp
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.
---
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 for Claude Desktop, Cursor, and more.
---
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.
---
The BC Code Intelligence specialists are ready to help. Just type naturally - here are some examples:
---
| 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 |
---
| Topic | Link |
|-------|------|
| Full Installation Options | Installation Guide |
| Common Scenarios | Usage Patterns |
| All MCP Tools | Tools Reference |
| Company Standards | Enterprise Configuration |
| Structured Workflows | Methodology Framework |
| Troubleshooting | Common Issues |
---
- 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
---
See the Contributing Guide for how to contribute to this project.
MIT License - see LICENSE for details.