Free cookie consent management tool by TermsFeed

Appian MCP Server Security

On This Page

This page is for system administrators, security teams, and compliance reviewers. It describes how Appian MCP Server enforces security across authentication, object access, and data queries.

Authentication methods for Appian MCP Server

Appian MCP Server supports two ways to authenticate connections. The authenticated identity determines which tools are visible and what data is accessible.

For details on monitoring MCP activity across both authentication methods, see Monitor Appian MCP Server.

OAuth 2.0 authentication

OAuth 2.0 authenticates each MCP connection as the signed-in Appian user. A user authorizes an authorization code client through Appian's sign-in page, and Appian issues an access token scoped to that user. MCP requests run with that user's permissions, and audit logs attribute actions to the individual.

For setup instructions, see Set up OAuth 2.0 authentication.

Service account authentication

Service account authentication uses an API key to authenticate all MCP connections under a single Appian service account. The service account's permissions and group membership determine tool visibility and data access for all connected AI applications.

Because every connection shares one identity, audit logs cannot attribute actions to individual users. If you need per-user attribution, use OAuth 2.0.

For setup instructions, see Set up service account API key authentication.

Object security for MCP tools

Appian MCP Server respects object security for all MCP-enabled design objects. The authenticating user must have the appropriate permission level for each design object type for it to appear as an available MCP tool.

The authenticating user must have the following permissions for each design object type:

Object Required permission
AI agents Permission to view the AI agent and all of its underlying tools.
Business processes At least Viewer permission for the business process and the process artifacts.
Expression rules At least Viewer permission to the expression rule.
Process models Initiator permission to the process model.
Record types At least Viewer permission to the record type, and the appropriate record-level and field-level security.

Caution:  Record types with record-level security expressions are not accessible through Appian MCP Server. Replace the security expression with security rules to make the record data accessible.

If the authenticating user lacks the required permissions, the MCP tool does not appear in search results. The AI application cannot discover or invoke it.

Encryption for MCP connections

All Model Context Protocol (MCP) connections use HTTPS encryption. Data transmitted between the AI application and Appian MCP Server is encrypted in transit using the same TLS standards as other Appian platform connections.

Feedback