View this page in the latest version of Appian. Enable and Configure Appian MCP Server Share Share via LinkedIn Reddit Email Copy Link Print On This Page This page is for system administrators and explains how to enable and configure the Appian MCP Server. To set up Appian MCP Server: Enable Appian MCP Server in the Admin Console. Manage tool collections to control which capabilities are available to external AI applications. Make design objects available as MCP tools. Configure authentication so external AI applications can connect. Enable audit logging to record Appian MCP Server requests for monitoring and troubleshooting. Prerequisites for enabling Appian MCP Server Before you enable Appian MCP Server: Environment: Your environment must be an Appian Cloud environment. Self-managed environments are not supported. Role: You must be a system administrator. Appian version: Your environment must be running Appian 26.6 or later. Enable Appian MCP Server Appian MCP Server is disabled by default, so users cannot authenticate or connect external AI applications to the environment through Model Context Protocol (MCP). To enable Appian MCP Server: In the Admin Console, go to MCP Server. Enable Appian MCP Server. By default, all MCP server tool collections are enabled and the MCP server endpoint URL is displayed as <ENVIRONMENT_URL>/mcp. Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close 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. To manage tool collections: In the Admin Console, go to MCP Server. In the MCP Server Tool Collections section, enable or disable any of the following tool collections: 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. Enabling a tool collection makes the capability available on the environment, but individual design objects are not accessible until a developer makes the design objects available as MCP tools. Make design objects available as MCP tools Enabling tool collections makes capabilities available on the environment, but individual design objects are not accessible until a developer enables them. Each of the following design objects must be individually enabled before external AI applications can discover or call it through MCP: Process models Expression rules. AI agents. Record types. 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: In the Admin Console, go to Web API Authentication. Create a service account with an API key. 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 Note: Protect the API key as you would any credential. The API key grants access to all MCP tools visible to the service account. If compromised, regenerate the key immediately in Web API Authentication. Enable audit logging Appian MCP Server requests are not logged by default. To record Appian MCP Server activity, you need to enable Platform API trace logging in the Admin Console. 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 connections: In the Admin Console, go to MCP Server. 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 Was this page helpful? SHARE FEEDBACK Loading...