Appian MCP Server
Enables interaction with Appian applications through the Model Context Protocol, allowing querying and managing records, executing processes, and querying reports via natural language.
README
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
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 install
- Set up environment variables:
cp .env.example .env
# Edit .env with your Appian credentials
Configuration
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 build
Development
For development with automatic compilation:
npm run watch
Then in another terminal, start the server:
npm start
Running the MCP Server
Direct Execution
npm run dev
In VS Code
- Ensure the project is built:
npm run build - Use 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.ts - Add a new tool definition in the
ListToolsRequestSchemahandler insrc/index.ts - Add a new case in the
CallToolRequestSchemahandler to call your method - Rebuild:
npm run build
Security Considerations
- Store API keys securely (use environment variables or secret management)
- Never commit
.envfiles to version control - Use HTTPS for all Appian API communication
- Implement proper access controls in your LLM application
Troubleshooting
Connection Issues
- Verify your
APPIAN_TENANTis correct - Ensure 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
.envfile - Check that the API key hasn't expired
- Confirm proper authentication method is configured
Build Errors
- Ensure TypeScript is installed:
npm install - Check for TypeScript compilation errors:
npm run build
License
MIT
Resources
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.