ALM X++ MCP Server
v1.5.1D365 F&O: 90 AI tools over 200K+ objects, 25M+ cross-refs, 24M+ label translations.
Endpoint health
online- Last checked
- 11/20/2026, 9:16:55 AM
- Latency
- 371 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.alimbenhelal-pro%2Falm-xpp-mcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.alimbenhelal-pro/alm-xpp-mcp": {
"url": "https://api.almxpp.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
ado_analyze_pr_impact
[~] PRIORITY TRIGGER: Use this tool when the user says 'analyse PR', 'review PR', 'check PR', 'PR #', 'impact du PR', 'analyse la PR', 'what changed in PR', 'D365 impact of PR', 'code review PR', 'violations in PR', 'PR review'. NEVER call search_d365_code when 'PR' or 'Pull Request' + a number is mentioned. Analyse the full D365 F&O code impact of a Pull Request. Reads each changed file's CONTENT straight from the PR's source commit via the ADO REST API, so it reviews the PROPOSED (un-merged) code -- including brand-new files that do not yet exist on the target branch. DO NOT fall back to local `git show`/`git diff`: this tool already pulls the un-merged content over the API and analyses it against the indexed standard KB. When `includeSource` is true (the default), the FULL un-merged source of every analysed file is embedded in the output (one fenced block per file), so you have everything needed for a complete semantic review -- BP findings AND the actual code -- in a single call. NEVER run git to read the files. This matters for metadata-only PRs (tables/enums/menu items/reports): the BP engine is X++-centric and may report few violations on AOT XML, but the embedded source lets you review those changes properly. For every X++ class/table/form/extension modified in the PR: (1) Best Practice validation -- reports Critical and Warning violations. (2) Upgrade impact -- cross-references CoC targets, event handlers, and extensions against the D365 standard code. (3) Extension conflicts -- finds existing CoC/extensions that may conflict. (4) Produces a ready-to-post PR review comment addressed to the PR author. After reviewing, call `ado_post_pr_comment` to post the review (requires user confirmation). Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read).
Schema valid · SHA-256 412df87b9307…
View input schema
{ "type": "object", "properties": { "repositoryId": { "description": "Git repository name or ID.", "type": "string" }, "prId": { "description": "Pull Request ID (integer), e.g. 42.", "type": "integer" }, "project": { "description": "Optional: Azure DevOps project name. Falls back to DEVOPS_PROJECT env var.", "type": [ "string", "null" ], "default": null }, "includeWarnings": { "description": "Include Warning-level violations in addition to Critical (default: true). Set false for Critical-only.", "type": "boolean", "default": true }, "maxFilesDeep": { "description": "Max X++ files to fully analyse (default 10, max 20). Larger PRs get a summary for remaining files.", "type": "integer", "default": 10 }, "includeSource": { "description": "Embed the un-merged SOURCE of each analysed file in the output so the reviewer can do a full semantic code review without a local git checkout. Default true.", "type": "boolean", "default": true }, "sourceCharsPerFile": { "description": "Max characters of source to embed per file when includeSource is true (1000-40000, default 8000). Larger files are truncated with a note.", "type": "integer", "default": 8000 } }, "required": [ "repositoryId", "prId" ] }
Connections
streamable-http
https://api.almxpp.com/mcp