Skip to main content
Glama
cmsappian123-bit

Appian MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APPIAN_TENANTNoYour Appian tenant name (e.g., 'mycompany')
APPIAN_API_KEYNoAPI key for authentication (recommended)
APPIAN_BASE_URLNoCustom Appian API base URL (optional)
APPIAN_CLIENT_IDNoOAuth client ID (alternative authentication)
APPIAN_CLIENT_SECRETNoOAuth client secret (alternative authentication)

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription
procurement_wizardSets Claude up as a strict multi-step intake wizard for creating new procurement workflows.
labelling_design_wizardSets 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

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cmsappian123-bit/MCP-Appian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server