Enable and Configure Appian MCP Server

System administrators enable Appian MCP Server, configure authentication, and manage tool collections in the Admin Console.

Appian MCP Server enforces the same object security, record-level security, and group membership as the Appian platform. Model Context Protocol (MCP) connections are subject to the same access controls as direct platform interactions. External AI applications that authenticate through MCP can only discover and use tools the authenticated user has permission to access.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Prerequisites for enabling Appian MCP Server

Before you enable Appian MCP Server:

• Role: You must have the system administrator role.
• Version: Your environment must be running Appian 26.6+.

Enable Appian MCP Server

Appian MCP Server is disabled by default. When disabled, users cannot authenticate or connect external AI applications to the environment through Model Context Protocol (MCP).

To enable Appian MCP Server:

1. In the Admin Console, go to MCP Server.
2. Set the Appian MCP Server toggle to enabled.

When enabled, the MCP server endpoint URL is displayed on the MCP Server page. The URL follows this format:

<ENVIRONMENT_URL>/mcp

Manage tool collections

Tool collections group related Model Context Protocol (MCP) system tools together. System administrators can enable or disable individual tool collections to control which capabilities are available to external AI applications.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

To manage tool collections:

1. In the Admin Console, go to MCP Server.
2. In the MCP Server Tool Collections section, enable or disable individual tool collections.

The following tool collections are available:

Tool Collection	Description
Call Process Models	Call process models and check their status.
Call Expression Rules	Evaluate expression rules.
Call AI Agents	Call AI agents and check their status.
Query Data Fabric	Query synced record types and related data.

How design objects become available

Developers control which objects the MCP server can access. Process models, expression rules, and AI agents must be explicitly enabled for the MCP server through each object's properties. Only objects that have been enabled can be discovered and called by MCP tools.

Record types work differently. Synced record types are accessible from the MCP server through the Query Data Fabric tool collection. Rather than requiring individual opt-in, record types rely on object-level, record-level, and field-level security to control which data is visible. Developers do not need to enable each record type separately—security rules determine what data the MCP server can read.

Record types that use direct data access or have a record-level security expression cannot be queried by external systems or agents.

To learn how to expose design objects as MCP tools, see Make Design Objects Available as MCP Tools.

For the full system tools reference, see MCP System Tools Reference.

Configure authentication

Appian MCP Server supports service account authentication. Model Context Protocol (MCP) connections authenticate using an API key tied to a service account. The service account's permissions determine which tools are visible and what data is accessible.

To set up authentication for Appian MCP Server:

1. In the Admin Console, go to Web API Authentication.
2. Create a service account with an API key.
3. Return to the MCP Server page and distribute the endpoint URL and JSON configuration to developers connecting AI agents.

The endpoint URL is displayed on the MCP Server page and follows this format:

<ENVIRONMENT_URL>/mcp

Audit logging

Appian MCP Server logs every Model Context Protocol (MCP) tool call to the existing audit infrastructure. Each log entry includes:

• Authenticated user: The user or service account that made the request.
• Tool invoked: The specific MCP tool that was called.
• Timestamp: When the tool call occurred.
• Outcome: Whether the call succeeded or failed.

Audit logs follow the same format and retention policies as existing Appian audit logs.

Disable Appian MCP Server

To disable Appian MCP Server Model Context Protocol (MCP) connections:

1. In the Admin Console, go to MCP Server.
2. Set the Application MCP Server toggle to disabled.

When disabled:

• External AI applications cannot authenticate or connect.
• Existing MCP tool configurations on design objects are preserved but inactive.
• If re-enabled, all previously configured tools become available again without reconfiguration.

Troubleshoot Appian MCP Server

The following table describes common Model Context Protocol (MCP) connection issues and resolutions:

Symptom	Likely cause	Resolution
External AI application cannot connect	Appian MCP Server is disabled	Enable the server in the Admin Console under MCP Server.
External AI application cannot connect	Invalid or expired API key	Regenerate the API key in Web API Authentication and distribute the new credentials to developers.
User cannot see expected tools	User lacks object security permissions	Verify the service account or user has viewer access to the design objects that are enabled as MCP tools.
User cannot query record data	Record-level security restricts access	Record-level security is enforced on all MCP data fabric queries. Verify the authenticated user has access to the requested records.
Tool call returns no results	Tool collection is disabled	In the Admin Console, verify the relevant tool collection is enabled under MCP Server > MCP Server Tool Collections.

Feedback