DynamicsCrm.DevKit.Cli 4.12.34.56

  ____                              _           ____                  ____             _  ___ _     ____ _ _
 |  _ \ _   _ _ __   __ _ _ __ ___ (_) ___ ___ / ___|_ __ _ __ ___   |  _ \  _____   _| |/ (_) |_  / ___| (_)
 | | | | | | | '_ \ / _` | '_ ` _ \| |/ __/ __| |   | '__| '_ ` _ \  | | | |/ _ \ \ / / ' /| | __|| |   | | |
 | |_| | |_| | | | | (_| | | | | | | | (__\__ \ |___| |  | | | | | |_| |_| |  __/\ V /| . \| | |_ | |___| | |
 |____/ \__, |_| |_|\__,_|_| |_| |_|_|\___|___/\____|_|  |_| |_| |_(_)____/ \___| \_/ |_|\_\_|\__(_)____|_|_|
        |___/            https://github.com/phuocle/Dynamics-Crm-DevKit 4.12.34.56 Build: 30.06.2026 23:59:59

⚙️ DynamicsCrm.DevKit CLI

DynamicsCrm.DevKit CLI is the devkit .NET global tool for Dataverse deployment automation, code generation, solution packaging, web resource operations, report operations, and MCP hosting for AI-assisted Dataverse work.

✨ Highlights

• One command-line surface for server deployments, web resources, reports, generated code, modelbuilder output, and solution packaging.
• Modern Spectre.Console CLI with devkit <command> --option value syntax and compatibility with legacy /option:value arguments.
• Connection support through --conn, explicit auth options, project .env, PAC profiles, client secrets, SDK login, and MCP DEVKIT_* environment variables.
• MCP server built into the CLI, exposing 33 Dataverse tools across basic, standard, and advanced categories.
• Single-file web resource deployment using --file and --webresource, including TypeScript release output deployment when project build scripts are present.

📦 Install

dotnet tool install --global DynamicsCrm.DevKit.Cli

Update an existing installation:

dotnet tool update --global DynamicsCrm.DevKit.Cli

🧭 Commands

🔐 Authentication

Normal command connection values can be supplied by command-line options or project .env. Resolution order is explicit CLI arguments, then project .env, then validation error. The mcp command is the exception: it resolves explicit CLI arguments, then OS DEVKIT_* environment variables, then validation error.

For normal CLI commands, DevKit searches for a project .env file from the command directory upward. VSIX-created projects also create .env.example beside .env; commit .env.example, but keep .env local because it can contain secrets. When DevKit creates .env, it adds the absolute .env path to the nearest .gitignore if one exists.

🚀 Usage

devkit server --conn "AuthType=OAuth;..." --json "DynamicsCrm.DevKit.Cli.json" --profile DEBUG
devkit webresource --conn "AuthType=OAuth;..." --file ".\js\account.js" --webresource "new_/js/account.js"
devkit generator --auth FromPac --pacprofile DEV --json "DynamicsCrm.DevKit.Cli.json" --profile Account
devkit modelbuilder --auth FromPac --pacprofile DEV --json "DynamicsCrm.DevKit.Cli.json" --profile ALL
devkit solution --auth FromPac --pacprofile DEV --json "DynamicsCrm.DevKit.Cli.json" --profile Extract-Both

🤖 MCP Server

The mcp command turns devkit into a stdio MCP server for AI agents that need to inspect, operate, and safely customize Dataverse environments. The server writes operational logs to stderr and reserves stdout for the MCP protocol, which is the expected behavior for stdio MCP clients.

devkit mcp --auth FromPac --pacprofile DEV --category standard --dry-run
devkit mcp "DynamicsCrm.DevKit" --auth FromPac --pacprofile DEV --category standard --dry-run

Use standard with --dry-run as the default onboarding mode for AI agents. It gives the agent enough read/debugging capability to understand the environment while blocking mutating operations. Move to advanced only when the agent is intentionally allowed to change schema, app navigation, command bar, ribbon, or raw Web API behavior.

FromPac is supported by the MCP command through FromPacConnectionBuilder. It requires an existing PAC CLI auth profile name and does not require --url; the environment URL is resolved from %LOCALAPPDATA%\Microsoft\PowerAppsCLI\authprofiles_v2.json.

🧠 AI Agent Bootstrap

When an AI agent reads this repository and needs to configure MCP, use this sequence:

1. Install or update the CLI with dotnet tool install --global DynamicsCrm.DevKit.Cli or dotnet tool update --global DynamicsCrm.DevKit.Cli.
2. Choose an auth mode. FromPac is the simplest local developer setup when a PAC CLI profile already exists and has an active Dataverse environment; ClientSecret is the best unattended setup for a service principal.
3. Add the MCP client entry with command: "devkit" and args: ["mcp", "DynamicsCrm.DevKit", "--category", "standard", "--dry-run"].
4. Start the client and call whoami first to confirm the connected Dataverse organization.
5. Read MCP resources such as schema://fetchxml, schema://formxml, docs://data_operations_guide, docs://schema_tools_guide, docs://instructions_for_formxml, docs://instructions_for_views, and docs://instructions_for_manage_app before editing Dataverse metadata.

Quick checks that do not connect to Dataverse:

devkit mcp --setup-guide
devkit mcp --tools

🔌 MCP Client Config

Most MCP clients use one of these JSON shapes. Keep secrets in environment variables or your MCP client's secret store when possible. The FromPac examples intentionally omit DEVKIT_URL because MCP resolves the environment URL from the PAC CLI profile.

mcpServers style:

{
  "mcpServers": {
    "dynamicscrm-devkit": {
      "command": "devkit",
      "args": ["mcp", "DynamicsCrm.DevKit", "--category", "standard", "--dry-run"],
      "env": {
        "DEVKIT_AUTH_TYPE": "FromPac",
        "DEVKIT_PAC_PROFILE": "DEV"
      }
    }
  }
}

servers style:

{
  "servers": {
    "dynamicscrm-devkit": {
      "type": "stdio",
      "command": "devkit",
      "args": ["mcp", "DynamicsCrm.DevKit", "--category", "standard", "--dry-run"],
      "env": {
        "DEVKIT_AUTH_TYPE": "FromPac",
        "DEVKIT_PAC_PROFILE": "DEV"
      }
    }
  }
}

Service-principal configuration:

{
  "mcpServers": {
    "dynamicscrm-devkit": {
      "command": "devkit",
      "args": ["mcp", "DynamicsCrm.DevKit", "--category", "advanced"],
      "env": {
        "DEVKIT_AUTH_TYPE": "ClientSecret",
        "DEVKIT_URL": "https://org.crm.dynamics.com",
        "DEVKIT_CLIENT_ID": "00000000-0000-0000-0000-000000000000",
        "DEVKIT_CLIENT_SECRET": "client-secret"
      }
    }
  }
}

🔐 MCP Authentication

MCP resolves connection values from explicit command-line arguments first, then OS DEVKIT_* environment variables. MCP does not read project .env by default.

For FromPac, run pac auth list first and use the profile name shown there. If the selected profile does not contain a Dataverse environment URL, select an environment with PAC CLI before starting MCP.

Equivalent command-line form:

devkit mcp "DynamicsCrm.DevKit" --auth FromPac --pacprofile DEV --category standard --dry-run
devkit mcp "DynamicsCrm.DevKit" --auth ClientSecret --url "https://org.crm.dynamics.com" --clientid "<app-id>" --clientsecret "<secret>" --category advanced
devkit mcp "DynamicsCrm.DevKit" --conn "AuthType=OAuth;..." --category basic

🧰 Tool Categories

Tool categories are cumulative. standard includes every basic tool, and advanced includes every standard tool.

Basic tools:

whoami, get_tables, manage_choice, manage_record, create_records,
generate_demo_data, execute_fetchxml, search_records, parse_record_url

Standard tools:

publish_customizations, manage_form, manage_view, manage_role, get_messages,
manage_environment_variable, get_workflows, get_flows, get_business_process_flows,
get_business_rules, get_custom_apis, get_audit_history, get_solution_components,
get_plugin_trace_logs, get_system_jobs, get_plugins, manage_webresource

Advanced tools:

manage_app, upsert_table, upsert_column, upsert_relationship, execute_webapi,
manage_ribbon, manage_command

📚 MCP Resources

MCP resources are bundled with the server so AI agents can read the exact schema and workflow rules before generating XML or calling mutating tools.

⚙️ MCP Options

🛟 MCP Troubleshooting

🔗 Links

• Repository README
• NuGet package
• Visual Studio extension
• Companion tool
• Issues