Appian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPIAN_TENANT | No | Your Appian tenant name (e.g., 'mycompany') | |
| APPIAN_API_KEY | No | API key for authentication (recommended) | |
| APPIAN_BASE_URL | No | Custom Appian API base URL (optional) | |
| APPIAN_CLIENT_ID | No | OAuth client ID (alternative authentication) | |
| APPIAN_CLIENT_SECRET | No | OAuth client secret (alternative authentication) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recordsB | Retrieve records from an Appian application using record type name |
| get_appian_suppliersA | Fetches a list of active available suppliers from the Appian Data Fabric based on a given domain/category. |
| create_procurement_requestB | Submits a completely structured multi-step procurement form payload directly into Appian to start the workflow process. |
| create_labelling_requestB | Submits a completely populated multi-step Labelling Design Request payload directly into Appian to trigger validation and trial setup. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| procurement_wizard | Sets Claude up as a strict multi-step intake wizard for creating new procurement workflows. |
| labelling_design_wizard | Sets Claude up as a strict multi-step intake wizard for initiating Clinical Trial Labelling Design Requests. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.