Appian MCP Server
Allows interaction with Appian applications, providing tools for record management (create, read, update, delete), process execution, and report querying.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Appian MCP Server Show me the top 10 customer records from the CRM record type."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Appian MCP Server
A Model Context Protocol (MCP) server for seamless integration with Appian APIs using Node.js.
Overview
This MCP server provides a standardized interface to interact with Appian applications, allowing AI applications to:
Query and manage records
Create, update, and delete records
Execute processes
Query reports
Related MCP server: YingDao RPA MCP Server
Features
Record Management: Get, create, update, and delete Appian records
Process Execution: Execute Appian processes with input parameters
Report Querying: Query Appian reports with filters
TypeScript Support: Built with TypeScript for type safety
Error Handling: Comprehensive error handling and logging
Configurable Authentication: Support for API keys and OAuth
Prerequisites
Node.js 16 or higher
npm or yarn
Appian configuration (tenant, credentials)
Installation
Clone or navigate to the project directory
Install dependencies:
npm installSet up environment variables:
cp .env.example .env
# Edit .env with your Appian credentialsConfiguration
Environment Variables
APPIAN_TENANT: Your Appian tenant name (e.g., "mycompany")APPIAN_API_KEY: API key for authentication (recommended)APPIAN_CLIENT_ID: OAuth client ID (alternative authentication)APPIAN_CLIENT_SECRET: OAuth client secret (alternative authentication)APPIAN_BASE_URL: Custom Appian API base URL (optional)
MCP Configuration
The .vscode/mcp.json file configures the MCP server for use with LLM applications:
{
"servers": {
"appian-mcp-server": {
"type": "stdio",
"command": "node",
"args": ["dist/index.js"]
}
}
}Available Tools
get_records
Retrieve records from an Appian record type.
Parameters:
recordType(string, required): The name of the Appian record typelimit(integer, optional): Maximum number of records to return (default: 100)offset(integer, optional): Number of records to skip for pagination (default: 0)
create_record
Create a new record in an Appian application.
Parameters:
recordType(string, required): The name of the Appian record typedata(object, required): The record data to create
update_record
Update an existing record.
Parameters:
recordType(string, required): The name of the Appian record typerecordId(string, required): The ID of the record to updatedata(object, required): The fields to update
delete_record
Delete a record from an Appian application.
Parameters:
recordType(string, required): The name of the Appian record typerecordId(string, required): The ID of the record to delete
execute_process
Execute an Appian process.
Parameters:
processName(string, required): The name of the Appian processinputs(object, optional): Input parameters for the process
query_report
Query an Appian report.
Parameters:
reportName(string, required): The name of the Appian reportfilters(object, optional): Filters to apply to the report
Building
Build the TypeScript source to JavaScript:
npm run buildDevelopment
For development with automatic compilation:
npm run watchThen in another terminal, start the server:
npm startRunning the MCP Server
Direct Execution
npm run devIn VS Code
Ensure the project is built:
npm run buildUse the MCP inspector tool or connect through an LLM application
The server will communicate via stdio
API Integration
The server uses axios for HTTP communication with Appian REST APIs. Update the appian-client.ts file to add additional Appian operations as needed.
Error Handling
The server includes comprehensive error handling for:
Network failures
Authentication errors
Invalid record types or IDs
API validation errors
Errors are returned in the MCP response format with detailed error messages.
Extending the Server
To add new Appian operations:
Add a new method to
AppianClientinsrc/appian-client.tsAdd a new tool definition in the
ListToolsRequestSchemahandler insrc/index.tsAdd a new case in the
CallToolRequestSchemahandler to call your methodRebuild:
npm run build
Security Considerations
Store API keys securely (use environment variables or secret management)
Never commit
.envfiles to version controlUse HTTPS for all Appian API communication
Implement proper access controls in your LLM application
Troubleshooting
Connection Issues
Verify your
APPIAN_TENANTis correctEnsure your API key is valid and has necessary permissions
Check that your Appian instance is accessible from your network
Authentication Errors
Verify credentials in your
.envfileCheck that the API key hasn't expired
Confirm proper authentication method is configured
Build Errors
Ensure TypeScript is installed:
npm installCheck for TypeScript compilation errors:
npm run build
License
MIT
Resources
Available Tools
4 toolscreate_labelling_requestB
Submits a completely populated multi-step Labelling Design Request payload directly into Appian to trigger validation and trial setup.
Inputs: labellingRequest (required).
create_procurement_requestB
Submits a completely structured multi-step procurement form payload directly into Appian to start the workflow process.
Inputs: procurementRequest (required).
get_appian_suppliersA
Fetches a list of active available suppliers from the Appian Data Fabric based on a given domain/category.
Inputs: category (required).
get_recordsB
Retrieve records from an Appian application using record type name
Inputs: recordName (required), pageSize.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct action: two creation operations for different request types and two retrieval operations for different data sources. Descriptions clearly differentiate their purposes, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern: create_labelling_request, create_procurement_request, get_appian_suppliers, get_records. No mixing of conventions.
Four tools is well-scoped for an Appian integration server, covering essential creation and retrieval operations without unnecessary bloat or deficiency.
The tool set covers the primary actions of submitting requests and fetching data, but lacks update/delete capabilities or status tracking for submitted requests, which could be considered minor gaps for full workflow coverage.
Related MCP Connectors
Ask your Quickbase apps in plain language. Read-only by default; writes need human approval.
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Query your org's data in natural language — read-only MCP access to SQL, NoSQL, files & warehouses.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- AlicenseBqualityBmaintenanceTransforms complex Pega Platform interactions into intuitive, conversational experiences by exposing Pega DX APIs through the standardized Model Context Protocol, enabling AI applications to interact with Pega through natural language.67345 npm23Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI to execute RPA applications and workflows through the Model Context Protocol, supporting both local and cloud modes.7 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to access, search, and analyze Spark Desktop meeting transcripts and emails through natural language via the Model Context Protocol.11-
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with Home Assistant for managing entities, automations, services, and dashboards via the Model Context Protocol.154 npmMIT