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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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