MCP Tool D365 Artifact Engine

The fastest way to build D365 F&O artifacts. Period.

generate_fo_artifacts

Production-ready tables, forms, security, data entities, and extensions — from structured specs to deployable XML in under 2 seconds. 15 artifact types. Up to 500 per call. Near-zero structural errors. Deploy script included.

Get Your API Key See What It Generates Setup Guide

The Problem

XML Scaffolding Is Where D365 Development Wastes the Most Time

A simple "add a new entity with a form and security" means 10–15 XML files — each one an opportunity to get a namespace wrong, misspell an EDT reference, or forget a required empty element.

MANUAL

Developers Spend 30–60 min on Boilerplate

Experienced developers hand-craft AxTable, AxEdt, AxEnum, AxForm, AxMenuItemDisplay, AxSecurityPrivilege XML — each with its own schema and naming conventions — before writing a single line of business logic.

AI AGENT

AI Agents Hallucinate XML Structure

Without exact XML schema knowledge, coding agents hallucinate element names, nest nodes incorrectly, and produce artifacts that fail on first build. The fix-loop burns tokens: read error, guess fix, rebuild, repeat.

COST

15,000–30,000 Tokens Wasted

Every token your AI agent spends crafting XML by hand is a token not spent on business logic. Structural scaffolding consumes 40–60% of a development cycle's tokens and time.

How It Works

Three Steps. Plain English In, Deployed Artifacts Out.

You describe what you need. Your AI agent handles the API call. The deploy script places files automatically.

1 →

Describe

Tell your AI agent what you need: “Create a VehicleTable with VehicleId, Make, Model, Year”

2 →

Generate

The agent calls generate_fo_artifacts — production-ready XML back in under 2 seconds

3

Deploy

The AI agent automatically runs the included deploy script to place files in your D365 metadata folder. Start writing business logic.

Under the Hood

A Structured API, Not a Prompt

Define your artifacts as typed task objects. The engine returns production-ready XML files with a deployment script.

What You Send

A model name, a prefix, and an array of task definitions. Each task specifies the artifact type and its properties.

input · tasks 
{
  "model_name": "ContosoFleet",
  "model_prefix": "CFlt",
  "tasks": [
    { "type": "table",
      "name": "Vehicle",
      "fields": [
        { "name": "VehicleId", "type": "string", "size": 20 },
        { "name": "Make", "type": "string", "size": 60 }
      ] },
    { "type": "form",
      "name": "Vehicle",
      "style": "ListDetails" },
    { "type": "security_privilege",
      "name": "VehicleMaintain" }
  ]
}
→ < 2 sec

What You Get Back

Base64-encoded XML files ready to write to your metadata folder, plus a PowerShell deployment script.

output · files 
CFltVehicle/
  AxTable/       CFltVehicle.xml
  AxEdt/         CFltVehicleId.xml
  AxForm/        CFltVehicle.xml
  AxMenuItemDisplay/ CFltVehicle.xml
  AxSecurityPrivilege/
                 CFltVehicleMaintain.xml
  deploy.ps1     # one-command deploy

Pass bare names like "Vehicle" and "VehicleId" — the engine prepends your model prefix to every AOT object and rewrites all internal references to match.

Artifact Coverage

15 D365 F&O Artifact Types

New objects and extensions of standard D365 objects — all from one API call

T

Table

AxTable with fields, indexes, relations

E

EDT

Extended Data Types for consistent fields

N

Enum

Enumerations for dropdowns and status

F

Form

UI forms with data sources and layout

L

Label

Label resource files for localization

M

Menu Item

Navigation items for form access

D

Data Entity

OData entities with staging tables

P

Privilege

Security privileges with EntryPoints

U

Duty

Security duties grouping privileges

R

Role

Security roles for access control

Extensions supported: Table Extension, Form Extension, Data Entity Extension, Field (companion definitions for tables and extensions)

Differentiators

What Makes It Different

Not just code generation — a deterministic artifact creation engine

01

Naming Is Automatic

Pass bare names like "Vehicle" and "VehicleId." The engine prepends your model name to every AOT object and rewrites all internal references to match. You never touch a model prefix manually.

02

Near-Zero Structural Errors

Output matches the D365 compiler schema by construction, not by trial and error. Cross-references between artifacts in the same batch resolve correctly. No dangling references, no missing namespaces.

03

Deploy Script Included

Every response contains a PowerShell script that copies the generated files to your metadata folder, preserving the D365 directory structure — AxTable, AxEdt, AxEnum, AxForm, and more.

04

Up to 500 Artifacts per Call

A complete module — tables, fields, EDTs, enums, forms, menu items, security stack, data entities — in a single request. Sub-2-second execution. Deterministic output.

The Numbers

Side-by-Side Comparison

A typical customization: new table, 8 fields, list-details form, menu item, maintain/view privileges, duty, and data entity (~20 artifact files)

Approach Time Build Errors Token Cost
Manual XML by developer 30–60 min 2–5 typical N/A
AI agent writing XML 5–15 min 3–8 typical 15,000–30,000
generate_fo_artifacts < 2 sec 0 ~2,000

Real Scenario

Add a Vendor Rating System

Track vendor quality ratings with a custom table, expose it on the vendor form, and make it available for import via data entity.

Without generate_fo_artifacts: Open Application Explorer, study existing XML schemas, hand-craft AxEdt for VendRatingId, AxEnum for VendRatingLevel, AxTable with fields, AxForm with data source wiring and grid layout, AxMenuItemDisplay, two AxSecurityPrivileges, AxSecurityDuty, a form extension for VendTable, and AxDataEntity. Build, fix 2–5 errors, rebuild.

With generate_fo_artifacts: Query fo-semantic to understand existing VendTable patterns (2 sec). Call generate_fo_artifacts with 15 tasks (2 sec). Deploy generated files (5 sec). Write X++ business logic (15 min). Build — clean first build (3 min).

75%
Time Saved
85%+
Token Cost Reduced
0
Structural Build Errors

Integration

Standalone MCP Tool + AutoXPP

Use it on its own to skip the XML grind. Or let AutoXPP call it for you as part of the full autonomous lifecycle.

Standalone

generate_fo_artifacts is a standard MCP tool. Connect it to Claude Code, Cursor, Windsurf, VS Code, Claude Desktop — any MCP-compatible client. No AutoXPP required.

Free users and CloudForge Stage 1 subscribers get limited generate_fo_artifacts MCP calls. Your AI agent calls it directly whenever it needs D365 artifacts — no orchestration framework needed.

With AutoXPP

AutoXPP subscribers get unlimited generate_fo_artifacts usage included in their plan. AutoXPP's coding skill calls it automatically on every structural work item — no metering friction during autonomous development cycles.

The structural layer that used to consume 40–60% of a development cycle now costs a single API call. The AI agent's full capacity goes to business logic.

AutoXPP = unlimited generate_fo_artifacts + full autonomous lifecycle

Knowledge Foundation

generate_fo_artifacts uses fo-semantic's 150,000-artifact knowledge base internally. The engine runs server-side with no local codebase — when it needs D365 structural knowledge, it queries fo-semantic. This is how it produces production-ready XML in under 2 seconds without studying the full codebase.

Get Started

Ready to Skip the XML Grind?

Standard MCP tool — works with any MCP-compatible AI coding client.

Get Your API Key Setup Guide Explore AutoXPP for Unlimited Usage

Questions? contact@xplusplus.ai