Enable and Configure Appian MCP Server

This page is for system administrators and explains how to enable and configure the Appian MCP Server.

To set up Appian MCP Server:

1. Enable Appian MCP Server in the Admin Console.
2. Manage tool collections to control which capabilities are available to external AI applications.
3. Configure authentication so external AI applications can connect.
4. 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:

1. In your Appian environment, open the navigation menu and select Admin Console.
2. In the Admin Console, go to MCP Server.

3. 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:

1. In the Admin Console, go to MCP Server.

2. 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.
   Analyze Business Processes	Query, analyze, and build reports for business processes and record data in Process HQ.

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.

Configure authentication

Appian MCP Server supports two authentication methods for Model Context Protocol (MCP) connections. Enabling the server and registering clients are separate steps—enabling the Appian MCP Server makes MCP available on the environment, while client registration determines who can connect and how.

Set up OAuth 2.0 authentication

To let users connect as themselves:

1. In the Admin Console, go to Web API Authentication.
2. Create an OAuth 2.0 Authorization Code grant client with the mcp scope.
3. Share the client ID and the authorization and token endpoints with the users who will connect.

With OAuth 2.0, MCP requests run with each signed-in user's Appian permissions rather than a shared service account's permissions.

Set up service account API key authentication

To let AI applications connect as a shared service account:

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 applications.

Troubleshoot authentication setup

If users cannot connect with user-scoped OAuth, verify the following in the Admin Console:

• The authorization code client is active and uses the mcp scope.
• The user is a member of one of the client's required groups.
• The redirect URI the client uses is registered on the client.

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.

For the full monitoring reference, see Monitor Appian MCP Server.

Disable Appian MCP Server

To disable Appian MCP Server connections:

1. In the Admin Console, go to MCP Server.
2. Set the Appian 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