MCP (Model Context Protocol) server for AL Object ID management in Microsoft Dynamics 365 Business Central development.
Add to Claude Code with one command:
# Standard mode (8 tools) - Recommended for teams
claude mcp add objid @sshadows/objid-mcp --env MCP_MODE=standard
# Lite mode (4 tools) - For individual developers
claude mcp add objid @sshadows/objid-mcp --env MCP_MODE=liteThat's it! The server will be available in Claude Code immediately.
If you prefer to configure manually, add to your MCP settings JSON:
{
"mcpServers": {
"objid": {
"command": "npx",
"args": ["-y", "@sshadows/objid-mcp"],
"env": {
"MCP_MODE": "standard"
}
}
}
}{
"mcpServers": {
"objid": {
"command": "npx",
"args": ["-y", "@sshadows/objid-mcp"],
"env": {
"MCP_MODE": "lite"
}
}
}
}{
"mcpServers": {
"objid": {
"command": "npx",
"args": ["-y", "@sshadows/objid-mcp"],
"env": {
"MCP_MODE": "standard",
"BACKEND_URL": "https://your-backend.azurewebsites.net",
"BACKEND_API_KEY": "your-api-key",
"LOG_LEVEL": "info"
}
}
}
}authorization- Manage app authorization with backendconfig- Read and write .objidconfig filesallocate_id- Allocate object IDs for AL objectsanalyze_workspace- Analyze workspace structure and apps
pool- Manage app pools for team collaborationconsumption- Get consumption reports and statisticssync- Synchronize object IDs with backendlog- Retrieve activity logs and audit trail
Manage app authorization with the AL Object ID Ninja backend:
- Check authorization status
- Authorize apps with backend
- Manage authorization keys
Configuration file management:
- Read .objidconfig files
- Write configuration changes
- Manage AL object ID ranges
Object ID allocation:
- Get next available object ID
- Support for all AL object types
- Range-aware allocation
Workspace analysis:
- Scan for AL apps
- Detect configurations
- Analyze project structure
App pool management for teams:
- Create app pools
- Join existing pools
- Leave pools
- Get pool information
Usage tracking and reporting:
- Get detailed consumption statistics
- Track ID usage over time
- Generate usage reports
Backend synchronization:
- Sync object IDs with backend
- Check synchronization status
- Force synchronization
Activity logging and audit:
- Retrieve activity logs
- Filter by event type, user, or date
- Audit trail for compliance
| Variable | Description | Default |
|---|---|---|
MCP_MODE |
Server mode: lite or standard |
lite |
BACKEND_URL |
Custom backend URL | https://vjekocom-alext-weu.azurewebsites.net |
BACKEND_API_KEY |
API key for custom backend | None (not required for default backend) |
LOG_LEVEL |
Logging level: error, warn, info, debug |
info |
CACHE_ENABLED |
Enable response caching | true |
CACHE_TTL |
Cache time-to-live in milliseconds | 300000 (5 minutes) |
The AL Object ID Ninja MCP Server provides intelligent object ID management for Business Central AL development. It integrates with the AL Object ID Ninja backend to prevent ID collisions, track usage, and enable team collaboration.
- Collision Prevention - Automatic ID conflict detection
- Team Collaboration - Shared ID pools for teams
- Usage Tracking - Comprehensive consumption reports
- Git Integration - Automatic app identification via Git
- Zero Configuration - Works out-of-the-box with default backend
# Clone repository
git clone https://github.com/SShadowS/objid-mcp.git
cd objid-mcp/mcp-server
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm testnpm test # Run test suite
npm run test:e2e # Run E2E tests
npm run typecheck # TypeScript type checking
npm run lint # ESLint
npm run prerelease # Full release checkmcp-server/
βββ src/v2/
β βββ server.ts # Main entry point
β βββ tools/ # Tool implementations
β β βββ lite/ # LITE mode tools
β β βββ standard/ # STANDARD mode tools
β βββ lib/ # Core libraries
βββ tests/v2/ # Test suites
βββ dist/v2/ # Compiled output
Contributions are welcome! Please open issues or pull requests for bugs, features, or improvements.
MIT
Based on the original AL Object ID Ninja by Vjekoslav BabiΔ