mcp_publish_customizations

Summary

Field	Value
Tool name	publish_customizations
MCP title	Publish customizations to make changes visible
Category	standard
Implementation	DynamicsCrm.DevKit.Cli/Mcp/Tools/PublishCustomizationsTool.cs
Estimated token count	~234 tokens (tools/list tool JSON, o200k_base, measured 2026-06-18)
Last verified	2026-06-18

MCP Tool Description (Exact)

Publish Dataverse metadata changes (entities, attributes, forms, views, option sets, relationships, model-driven apps). Specific publish is faster than PublishAll. Idempotent.

WHEN TO USE:
- After upsert_* / execute_webapi metadata changes when auto_publish=false
- After manage_app changes when the user is ready to publish the appmodule
- When user reports changes not showing up
- Batch many changes then publish once at the end

Parameters

Name	Type	Required	Default	Description
entities	string	No	""	Comma-separated entity Display Names or logical names (e.g. 'Account,contact'). Empty with no other targets = PublishAll.
include_global_optionset	boolean	No	false	Also publish global option sets.
include_sitemap	boolean	No	false	Also publish sitemap.
appmodules	string	No	""	Comma-separated appmodule GUIDs, Display Names, or unique names for model-driven apps.

Input Schema

{
  "type": "object",
  "properties": {
    "entities": {
      "type": "string",
      "description": "Comma-separated entity Display Names or logical names (e.g. 'Account,contact'). Empty with no other targets = PublishAll.",
      "default": ""
    },
    "include_global_optionset": {
      "type": "boolean",
      "description": "Also publish global option sets.",
      "default": false
    },
    "include_sitemap": {
      "type": "boolean",
      "description": "Also publish sitemap.",
      "default": false
    },
    "appmodules": {
      "type": "string",
      "description": "Comma-separated appmodule GUIDs, Display Names, or unique names for model-driven apps.",
      "default": ""
    }
  },
  "required": []
}

Related MCP Resources

This tool does not require any MCP resources.

When To Use

• After upsert_* / execute_webapi metadata changes when auto_publish=false
• After manage_app changes when the user is ready to publish the appmodule
• When user reports changes not showing up
• Batch many changes then publish once at the end

Notes

• Use the exact MCP description and parameter schema above as the authoritative contract.

Example

{
  "entities": "string"
}

Output

Returns CallToolResult from the MCP server. The response content and structured fields follow the tool implementation and model returned by PublishCustomizationsTool.publish_customizations.

Prompt Examples

• "Publish customizations for Account and Contact only."
• "Publish this model-driven app after metadata and sitemap changes."
• "Run a full publish because recent changes are not visible in the app."