Appian Dev MCP

Appian developers increasingly want to work alongside AI coding assistants, but those assistants have no safe, structured way to interact with an Appian environment. Appian Dev MCP closes that gap: it lets you drive Appian design work through natural language in any MCP-compatible AI client (such as Claude). Instead of clicking through Appian Designer object by object, you can ask your assistant to scaffold a new application, create record types and their backing database tables, add expression rules and interfaces, configure constants and integrations, or make repetitive and bulk changes — accelerating prototyping, application scaffolding, and routine development. Because the MCP server runs in your environment and acts as the signed-in developer, all work stays within your site and your existing permission boundaries.

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

2. Broad design-object coverage (120+ tools) — list, read, create, update, and delete Applications, Record Types (including database tables, fields, relationships, views, and actions), Constants (including list-typed), Expression Rules, Interfaces, Sites, Web APIs, Integrations, Connected Systems, Process Models, Groups, Folders, and Documents.

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

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

Remember to reinstall the MCP server based on the bundle in the plugin.

Notable:

• Creating rules, interfaces, or constants in an app where objects have previously been deleted no longer fails.
• Interface and expression rule tools now support an expressionFilePath parameter. When provided, the SAIL expression is written to (or read from) a file on disk instead of passed inline. This is both faster and uses fewer tokens.

New Features

• You can now view and set default values for process variables using updateProcessModel.
• Process model connections now support activity chaining, labels, and two other flags.
• Node inputs can now be set to Integer, Boolean, Decimal, and other types, not just Text.
• createExpressionRule, createInterface, and createConstant now accept a parentFolderUuid parameter.

Bug Fixes

• Creating a POST Web API no longer returns an error
• Explicit PK values are now supported when inserting record data. Previously explicit PK values were silently ignored and auto-increment was always used.
• The Write Records smart service node now correctly applies default values for User and Timestamp fields when set to an empty string
• listIntegrations now returns only actual integrations. Previously it returned too many objects
• listApplicationObjects no longer silently truncates results at 200 per object type
• updateProcessModel now correctly validates partial updates without requiring you to resend the entire model. Previously, omitting unchanged sections could trigger spurious validation errors.
• Folder tools now work with all folder types to list, update, and delete. Previously only a subset was recognized. searchFolders now also searches the Knowledge Center tree, not just Rules folders.
• testInterface now correctly handles record-type inputs. Previously passing a record type value as a test input caused a deserialization failure.
• Creating or updating integrations that use multipart request bodies no longer produces broken integration objects