Deploy MCP Tool Configurations

This page is for developers. It describes how to deploy Model Context Protocol (MCP) tool configurations between Appian environments as part of standard design object packages.

Appian MCP Server enforces the same object security, record-level security, and group membership as the Appian platform. MCP tool configuration metadata is stored as part of the design object. You do not need to manually re-enable MCP tools after deploying to a new environment.

How MCP configurations deploy

When you deploy a design object that has been made available as a Model Context Protocol (MCP) tool, the MCP configuration deploys with the object automatically. The following metadata travels with the design object:

• MCP enabled status: Whether the object is enabled as an MCP tool.

The design object's description is used as the MCP tool description and deploys with the object automatically.

No separate deployment step is required for MCP configurations.

Compare and Deploy behavior

Model Context Protocol (MCP)-related changes appear in the Compare and Deploy page alongside other design object changes. When reviewing a deployment package, you can see:

• Whether a design object has been newly enabled as an MCP tool.
• Whether the MCP enabled status has been changed (enabled or disabled).

Target environment requirements

For Model Context Protocol (MCP) tool configurations to become active in the target environment, the following condition must be met:

• Appian MCP Server must be enabled: The system administrator must enable Appian MCP Server in the target environment's Admin Console.

If Appian MCP Server is disabled in the target environment, the MCP tool configuration is preserved on the design object but inactive. The tool becomes available automatically when a system administrator enables Appian MCP Server—no redeployment is required.

Admin Console settings deployment

Admin Console Model Context Protocol (MCP) settings are separate from design object deployments. The following settings are managed independently:

• MCP server toggle: Enabled or disabled per environment by the system administrator.
• Tool collection enablement: Which tool collections (Call Process Models, Call Expression Rules, Call AI Agents, Query Data Fabric) are active.

Admin Console settings deploy separately from application packages. For more details on application deployment, see Deploying Applications.

Deployment scenarios

The following table describes common Model Context Protocol (MCP) deployment scenarios and the expected behavior:

Scenario	Behavior
Deploy MCP-enabled object to environment where Appian MCP Server is enabled	Tool becomes available immediately after deployment.
Deploy MCP-enabled object to environment where Appian MCP Server is disabled	MCP configuration is preserved but inactive. Tool becomes available when Appian MCP Server is enabled.
Deploy updated tool description to target environment	The tool description is updated on the target environment. External AI applications see the new description on their next tool discovery call.
Deploy object with MCP disabled (previously enabled in target)	The tool is removed from Appian MCP Server in the target environment. External AI applications can no longer discover or invoke it.

Feedback