Skip to content
Back to search

FoArtifacts

An MCP server for D365 Finance & Operations development

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 18 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/dizx/FoArtifacts with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/dizx/FoArtifacts'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dizx--foartifacts/badge.svg)](/listings/dizx--foartifacts)

HTML

<a href="/listings/dizx--foartifacts"><img src="/api/listings/dizx--foartifacts/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

dotnet publish src/FoArtifacts -c Release -o C:\tools\fo-artifacts

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 142 lines
  1. # fo-artifacts
  2. An MCP server for D365 Finance & Operations development. One tool, `generate_fo_artifacts`, creates
  3. a whole feature — enums, EDTs, tables, forms, menu items, security, entities and more — in one call:
  4. - bare names get your model prefix, and so do references between objects in the same batch;
  5. - tasks run in dependency order, with the index refreshed between stages;
  6. - if any task fails, every write of the batch is undone.
  7. It does not generate XML itself. It drives [d365fo-cli](https://github.com/dynamics365ninja/d365fo-cli)
  8. (`d365fo`), which does the per-object generation and keeps the undo journal.
  9. ## Requirements
  10. - .NET 10 SDK
  11. - `d365fo` installed and indexed (`d365fo index build`, `d365fo index extract`), with your models
  12. listed in `D365FO_CUSTOM_MODELS`. Tested against commit `b60ffdd65fd182d378bce396fbc9f14849f8ce62`
  13. of the fork [dizx/d365fo-cli](https://github.com/dizx/d365fo-cli): upstream `7b37a25` plus two fixes
  14. for writes through the bridge (forms were saved with empty tab pages, and bridge writes reported no
  15. file path). Build it with `scripts/build-d365fo.*`; an upstream build without those fixes breaks
  16. forms when the bridge is on.
  17. - On the dev VM: `D365FO_BRIDGE_ENABLED=1`, so files are written through the Metadata API and
  18. `datasource-method` / `control-method` work.
  19. ## Install
  20. ```powershell
  21. dotnet publish src/FoArtifacts -c Release -o C:\tools\fo-artifacts
  22. ```
  23. ## Configure your AI client
  24. The server reads the same environment variables as `d365fo`, plus:
  25. | Variable | Meaning | Default |
  26. |---|---|---|
  27. | `D365FO_CLI` | Full path of the `d365fo` executable | `d365fo` on `PATH` |
  28. | `FO_ARTIFACTS_TIMEOUT_SECONDS` | Time limit for each `d365fo` call | `120` |
  29. Claude Code (`.mcp.json` in your X++ repo):
  30. ```json
  31. {
  32. "mcpServers": {
  33. "fo-artifacts": {
  34. "command": "C:\\tools\\fo-artifacts\\FoArtifacts.exe",
  35. "env": {
  36. "D365FO_CLI": "C:\\tools\\d365fo\\d365fo.exe",
  37. "D365FO_PACKAGES_PATH": "K:\\AosService\\PackagesLocalDirectory",
  38. "D365FO_CUSTOM_MODELS": "ContosoFleet",
  39. "D365FO_BRIDGE_ENABLED": "1"
  40. }
  41. }
  42. }
  43. }
  44. ```
  45. VS Code / Visual Studio (`.vscode/mcp.json` or `.mcp.json`):
  46. ```json
  47. {
  48. "servers": {
  49. "fo-artifacts": {
  50. "type": "stdio",
  51. "command": "C:\\tools\\fo-artifacts\\FoArtifacts.exe",
  52. "env": { "D365FO_CLI": "C:\\tools\\d365fo\\d365fo.exe", "D365FO_CUSTOM_MODELS": "ContosoFleet", "D365FO_BRIDGE_ENABLED": "1" }
  53. }
  54. }
  55. }
  56. ```
  57. ## Using it
  58. Ask your agent for the feature in plain words ("a Vehicle table with VehicleId and Status, a
  59. list-details form, a menu item and maintain security"). It calls the tool with something like:
  60. ```json
  61. {
  62. "model": "ContosoFleet",
  63. "prefix": "CFlt",
  64. "tasks": [
  65. { "type": "enum", "name": "VehicleStatus", "options": { "value": ["Active:0", "Retired:1"] } },
  66. { "type": "edt", "name": "VehicleId", "options": { "base-type": "String", "size": 20 } },
  67. { "type": "table", "name": "Vehicle", "options": { "pattern": "main", "field": ["VehicleId:VehicleId:mandatory", "Status:VehicleStatus"] } },
  68. { "type": "form", "name": "Vehicle", "options": { "pattern": "SimpleListDetails", "table": "Vehicle", "field": ["VehicleId", "Status"] } },
  69. { "type": "menu-item", "name": "Vehicle", "options": { "object": "Vehicle" } },
  70. { "type": "privilege", "name": "VehicleMaintain", "options": { "entry-point": "Vehicle", "entry-kind": "MenuItemDisplay", "access": "Delete" } },
  71. { "type": "duty", "name": "VehicleMaintain", "options": { "privilege": "VehicleMaintain" } },
  72. { "type": "role", "name": "VehicleManager", "options": { "duty": "VehicleMaintain" } }
  73. ]
  74. }
  75. ```
  76. - `type` is any `d365fo generate` subcommand except the deprecated `simple-list`; `options` are its
  77. options without `--` (`d365fo generate <type> --help` lists them; run it in a terminal).
  78. - `extension` needs `options.kind` (Table, Form, …): it is passed before the name.
  79. - `table-relation` and `find-methods` edit an existing table; fo-artifacts finds its file.
  80. - `dry_run: true` returns the stages and exact `d365fo` commands without writing.
  81. On failure the result names the failing task, d365fo's error and hint, and whether the rollback
  82. succeeded. If the d365fo journal shows writes that are not from the batch (for example you ran
  83. `d365fo` by hand between two of its steps), nothing is undone and the written files are listed instead.
  84. `rolled_back: true` means every file the batch created is gone; files d365fo could not undo (for
  85. example a label file's `.label.txt`, which d365fo does not journal) are listed under `left_behind`.
  86. Known limits:
  87. - `add-to`, `into-role` and `out-*` options are refused: d365fo writes them without a journal entry.
  88. - `table-relation` and `find-methods` only change tables of the model being written; use an
  89. `extension` task for other models' tables.
  90. - A `d365fo` write to the same model by another process at the exact moment one of the batch's own
  91. commands runs cannot be told apart from that command's writes, and would be undone with the batch.
  92. ## Dev VM checklist
  93. Run once after installing, and after upgrading `d365fo`:
  94. 1. `d365fo doctor --output json` reports the index and packages path.
  95. 2. Time `d365fo index refresh --model <YourModel>`; the batch runs it once per stage.
  96. 3. Ask for a dry run of the Vehicle example above; check the commands.
  97. 4. Run it for real, then build the model in Visual Studio: it must build without hand fixes.
  98. 5. Run a batch whose last task has a bad option (e.g. `"bogus": "x"`); check that every file from
  99. the batch is gone and Visual Studio shows nothing new.
  100. 6. With the bridge on, run a batch with `datasource-method` and `control-method` tasks on one of your
  101. forms; check the methods appear, then run the failing batch from step 5 with them in it and check
  102. the form is restored.
  103. ## Development
  104. ```bash
  105. dotnet test --project tests/FoArtifacts.Tests
  106. D365FO_CLI="$(scripts/build-d365fo.sh)" dotnet test --project tests/FoArtifacts.IntegrationTests
  107. ```
  108. PowerShell (the script prints only the path; don't index into its output with `[-1]`, which picks
  109. the last character of a single string):
  110. ```powershell
  111. dotnet test --project tests/FoArtifacts.Tests
  112. $env:D365FO_CLI = .\scripts\build-d365fo.ps1
  113. dotnet test --project tests/FoArtifacts.IntegrationTests
  114. ```
  115. Integration tests run the pinned `d365fo` against a copy of its sample model and are skipped when
  116. `D365FO_CLI` is not set. When moving to a newer `d365fo`, change the commit in
  117. `scripts/build-d365fo.*` and `src/FoArtifacts.Core/reference-map.json`, then run both test projects.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.