Appian Dev MCP (read-only)

Overview

Appian Dev MCP (read-only) gives AI coding assistants structured, read-only access to an Appian environment — with no ability to create, modify, or delete anything. It's designed for production sites where you need to inspect applications, trace how objects are configured, or investigate incidents alongside an AI assistant, but must guarantee that nothing changes. Mutating tools aren't just disabled — they don't exist: the MCP server structurally cannot issue a create, update, or delete operation. Because it runs in your environment and acts as the signed-in user, all queries stay within your site and your existing permission boundaries.

Key Features & Functionality

Structurally read-only — 56 inspection tools (list, get, read). No create, update, delete, or test-execution tools are registered. This isn't a configuration toggle — the tools are absent from the server, giving production teams confidence that the assistant cannot make changes even if asked to.
Embedded, ready-to-run MCP server — install the plug-in, download the bundled server from it, and point any MCP-compatible AI client (e.g., Claude) at it. No separate infrastructure to stand up.
Production use cases — investigate how an application is built, trace record type relationships and security rules, review process model flows, audit group memberships, inspect integration configurations, or explore an unfamiliar environment during an incident — all through natural language.
Flexible authentication — HTTP Basic for standard accounts, or browser-based single sign-on (SSO) for environments that require it, capturing your session through a normal browser login.
Security-first by design — access is limited to Designer and administrator roles, and every operation executes under the authenticated user's own permissions, scoped to the objects they're allowed to see.

After installing the plugin, please use https://docs.appian.com/suite/help/26.5/devmcp.html for instructions on installation and use. Note: until late June 2026, using this on your site may require a support case to turn on the correct feature toggle.