D365 F&O MCP Server

Why

AI assistants excel at C#, Python, and JavaScript. X++ is different: your D365FO codebase is private, deeply customized, and invisible to every model — so AI confidently generates code that doesn't compile.

This server pre-indexes your entire D365FO installation (580 000+ symbols across standard, ISV, and custom models) and exposes it as 26 specialized MCP tools. Every signature, every CoC wrapper, every label, every form pattern — verified against your real metadata before the AI writes a single line.

Capabilities

Pattern-grounded form development

Forms are the hardest artifact to generate correctly — each pattern dictates required containers, ordering, and allowed sub-patterns. The form pattern engine makes it a guided pipeline:

flowchart LR
    A["object_patterns<br/>(domain=form, action=analyze)"] --> B["object_patterns<br/>(domain=form, action=spec)"]
    B --> C["generate_object<br/>objectType=form, cloneFrom"]
    C --> D["object_patterns<br/>(domain=form, action=validate) FP001–FP010"]
    D -->|clean| E["d365fo_file<br/>(action=create) write + project"]
    D -->|errors| C

Structural violations (wrong order, missing container, disallowed control) block the write — recommendations only warn. Mined pattern statistics from your own environment ground every suggestion in reality.

Quick Start

Pick your path:

Full walkthrough with all scenarios: docs/QUICK_START.md

# Local / hybrid install (on the D365FO VM)
git clone https://github.com/dynamics365ninja/d365fo-mcp-server.git K:\d365fo-mcp-server
cd K:\d365fo-mcp-server
npm install
cd bridge\D365MetadataBridge; dotnet build -c Release; cd ..\..   # C# bridge — required for writes
npm run build

# Local only — build the metadata index (skip for hybrid)
copy .env.example .env            # set PACKAGES_PATH, CUSTOM_MODELS
npm run extract-metadata
npm run build-database

UDE / Power Platform Tools? Run npm run select-config instead of editing PACKAGES_PATH.

Connect GitHub Copilot

1. Enable MCP servers in Copilot at github.com/settings/copilot/features
2. Visual Studio → Tools → Options → GitHub → Copilot → Enable MCP server integration in agent mode
3. Create %USERPROFILE%\.mcp.json:

{
  "servers": {
    "d365fo-azure": { "url": "https://your-server.azurewebsites.net/mcp/" },
    "d365fo-local": {
      "command": "node",
      "args": ["K:\\d365fo-mcp-server\\dist\\index.js"],
      "env": {
        "MCP_SERVER_MODE": "write-only",
        "D365FO_SOLUTIONS_PATH": "K:\\repos\\MySolution\\projects",
        "D365FO_WORKSPACE_PATH": "K:\\AosService\\PackagesLocalDirectory\\YourPackage\\YourModel"
      }
    }
  }
}

4. Copy the instruction files into a parent folder of your solutions (one copy covers everything beneath it):

Copy-Item -Path ".github" -Destination "C:\source\repos\" -Recurse

All options: docs/MCP_CONFIG.md

Connect Claude Code

claude mcp add-json --scope user d365fo-mcp-tools '{"type":"http","url":"https://your-server.azurewebsites.net/mcp/","alwaysLoad":true}'
Copy-Item "K:\d365fo-mcp-server\CLAUDE.template.md" "C:\source\repos\CLAUDE.md"

Stdio variant and troubleshooting: docs/CLAUDE_CODE_SETUP.md

Verify

Open the AI chat (Copilot Agent Mode / Claude Code) and ask:

What tables contain "CustAccount" field?

A search tool call returning results from your codebase = you're connected.

Azure Deployment

One shared instance for the whole team — the metadata index lives in Blob Storage and downloads automatically on startup.

Deployment guide: docs/SETUP_AZURE.md · CI/CD automation: docs/PIPELINES.md

Documentation

License

MIT