al-objid

The AL Object ID Ninja MCP Server provides a set of tools to manage AL Object IDs for Dynamics 365 Business Central development. It runs as a Model Context Protocol (MCP) server that can be deployed in standard mode (full feature set) or lite mode (reduced toolset). In standard mode, you gain access to eight tools for team collaboration and object ID governance, while lite mode offers a lean four-tool workflow suitable for individual developers. The server integrates with the AL Object ID Ninja backend to prevent ID collisions, monitor usage, and facilitate shared ID pools across a team, with options to point to a custom backend if needed. Tools are exposed through Claude Code or your MCP client, enabling programmatic allocation, configuration management, workspace analysis, and more depending on the mode you run.

Available tools in standard mode include: pool (team-based app pool management), consumption (detailed usage statistics), sync (object ID synchronization with a backend), and log (activity logs and audit trails). In lite mode, you have authorization (manage app authorization with the backend), config (read/write .objidconfig files and manage ID ranges), allocate_id (request next available IDs with range awareness), and analyze_workspace (scan and analyze AL projects). These tools can be invoked via the MCP interface by selecting the server and tool, enabling workflows from ID allocation to team collaboration and backend synchronization.

To use the server, configure the MCP as shown in the documentation (either via Claude Code quick add or the manual JSON configuration). With the standard mode configuration, your client will spawn the objid-mcp instance and expose the eight tools for your development team to interact with object IDs and related metadata. If you prefer a custom backend, you can provide environment variables such as BACKEND_URL, BACKEND_API_KEY, and LOG_LEVEL to tailor behavior and observability.

Prerequisites:

• Node.js and npm installed on your system
• Access to a command line or terminal
• Git (optional, for cloning repository)

Step-by-step installation:

1. Install Node.js and npm from https://nodejs.org/ (ensure npm is available in your PATH).
2. Clone the MCP server repository or download the release package:
   • git clone https://github.com/SShadowS/objid-mcp.git
   • cd objid-mcp/mcp-server
3. Install dependencies:
   • npm install
4. Build the project (if applicable):
   • npm run build
5. Run tests (optional but recommended):
   • npm test
6. Start the MCP server with standard mode configuration (as described in the README):
   • Ensure your environment is set up (see next section on env vars).
7. Verify the server is reachable via your MCP client (Claude Code or other MCP clients) using the provided mcp_config example.

Notes:

• If you prefer a different backend, you can adjust environment variables (BACKEND_URL, BACKEND_API_KEY, etc.) in your MCP configuration.
• For production deployments, consider setting LOG_LEVEL to info or debug as needed and enable CACHE_ENABLED if supported by your backend.

Environment variables and configuration: MCP_MODE selects the toolset (lite or standard). BACKEND_URL and BACKEND_API_KEY allow using a custom backend. LOG_LEVEL controls log verbosity. CACHE_ENABLED and CACHE_TTL manage response caching. When deploying, ensure the chosen MCP mode aligns with your team needs (lite for individuals, standard for teams). If you encounter issues, check logs for misconfigurations in MCP_MODE or backend connectivity. The default backend URL in this repository is set to a placeholder; override it if you are connecting to a different backend service. In Cloud/CI environments, ensure network access to any external backends and that Node dependencies are resolved during build and deployment.