How to Setup generate_fo_artifacts

Choose Your Path

Path 1

Standalone MCP Tool

Add generate_fo_artifacts to any MCP-compatible AI client — Claude Code, Cursor, Windsurf, VS Code, Claude Desktop. One JSON config, one API key.

Jump to setup steps ↓

Path 2

AutoXPP Subscriber

No additional setup needed. generate_fo_artifacts is already included in your AutoXPP installation. AutoXPP calls it automatically on every structural work item.

Learn more ↓

Standalone Setup

generate_fo_artifacts is a standard MCP tool. Add the following configuration to your AI coding client and start generating D365 artifacts immediately.

Get Your API Key
Sign in to xplusplus.ai and get your API key from the dashboard.
Get API Key
Add MCP Server Configuration
Open your AI client's MCP configuration file and add the autoxpp MCP server:

Config File Location

Claude Code: ~/.claude.json
Cursor: .cursor/mcp.json (project) or global settings
VS Code: ~/.claude.json (Claude extension) or client-specific
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

MCP Configuration

{ "mcpServers": { "autoxpp": { "type": "http", "url": "https://autoxpp.xplusplus.ai/mcp", "headers": { "Authorization": "Bearer your_api_key_here" } } } }

Configuration

Authorization header (required) — Your API key from xplusplus.ai, prefixed with Bearer
Restart Your AI Client
After saving the config file, restart your AI client so it picks up the new MCP server. No local installation needed — it connects directly to the xplusplus.ai cloud endpoint.
- Claude Code CLI: Close and reopen your terminal, then run claude
- VS Code: Reload the window (Ctrl+Shift+P → "Developer: Reload Window")
- Cursor: Restart Cursor or reload the MCP config
- Claude Desktop: Quit and reopen the app
Test the Connection
Ask your AI agent to generate a D365 artifact:

> Create a VehicleTable with fields VehicleId, Make, Model, Year > Generate a form for VehicleTable with a grid and header view > Create security privileges for Vehicle management

The agent will call generate_fo_artifacts and return production-ready XML files with a deployment script.

Usage Limits

Free users and CloudForge Stage 1 subscribers get limited generate_fo_artifacts MCP calls. AutoXPP subscribers get unlimited usage — AutoXPP's coding skill calls it automatically on every structural work item.

Already Using fo-semantic-mcp?

If you already have fo-semantic-mcp configured, add the autoxpp server as a second entry in your mcpServers object. Your AI agent gets D365 knowledge search and instant artifact creation side by side.

Both MCP Servers

{ "mcpServers": { "fo-semantic": { "command": "npx", "args": ["-y", "fo-semantic-mcp"], "env": { "FOINDEX_API_KEY": "your_api_key_here" } }, "autoxpp": { "type": "http", "url": "https://autoxpp.xplusplus.ai/mcp", "headers": { "Authorization": "Bearer your_api_key_here" } } } }

AutoXPP Subscribers

No Additional Setup Needed

generate_fo_artifacts is already included in your AutoXPP installation. AutoXPP's coding skill calls it automatically on every structural work item — tables, forms, security, data entities, extensions. No separate MCP config, no metering friction.

Learn About AutoXPP AutoXPP Installation Guide

Troubleshooting

MCP server not connecting?

Verify your API key is correct and prefixed with Bearer
Check that the URL is exactly https://autoxpp.xplusplus.ai/mcp
Ensure your AI client supports HTTP-type MCP servers
Make sure the JSON syntax is valid (use a JSON validator)

Generation fails or returns errors?

Check your API key has available quota
Ensure your task definitions include the required fields (artifact type, properties)
Try a simpler request first (single table with a few fields)

Config file not being read?

Check the file is in the correct location for your AI client
Verify the JSON is valid (no trailing commas, correct quoting)
Restart your AI client completely after making changes