# Appian MCP connector

Connect Appian to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list application packages, releases, deployments and inspections, start a deployment or inspection, and read a deployment log, with every call logged.

Source: https://elaichi.ai/connectors/appian/

## Facts

| | |
| --- | --- |
| Application | Appian |
| Category | Application Development |
| AI tools | 8 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Appian is connected

- List every Appian deployment that failed this week
- Show me the log for the latest Appian deployment
- Which Appian releases shipped this month?

## Connect Appian in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Appian.
2. Optionally set Share with, then press Connect.
3. Paste an Appian API key. One person generates a token in Appian and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Appian tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Appian MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Appian MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Appian MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Appian MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Appian MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Appian to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Appian tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Appian through Elaichi

### Check what shipped in the latest release

Release management. Ask which Appian releases went out this month and pull up the detail on any one of them without opening the release list yourself.

### Start a deployment from a chat

Platform engineering. Ask to deploy an application package to the target environment and get the new deployment back so you can follow it.

### Read a failed deployment log in plain words

IT operations. When a deployment fails, ask for its log by ID and get the reason explained instead of scrolling through the raw output.

### Run an inspection before anyone deploys

QA. Ask to inspect a package against the target environment, then list past inspections to see whether the same issues keep coming back.

### Find the right package to ship

Application developers. List every application package and confirm the one that is ready before a deployment is created against the wrong one.

### Answer an auditor on what deployed when

Change management. List deployments over a period and match them to releases, so the change record is written from Appian itself rather than from memory.

## Elaichi vs Zapier MCP vs Composio for Appian

All three can connect Appian to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Appian tools | Allow or restrict single Appian tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Appian call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Appian to Claude?

Connect Appian in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Appian signs in with an API key, so you paste the key from your Appian environment when you connect and that is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate.

### Does Appian work with ChatGPT and Cursor as well as Claude?

Yes. Appian is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client. Elaichi's own agent uses it too, so there is nothing to set up a second time.

### What can an AI agent actually do with my Appian data?

With Appian connected, an agent can list your application packages, releases, deployments and inspections, open one release or one deployment log by ID, and create a new deployment or inspection when you ask. In practice that means asking what shipped this month, why last night's deployment failed, or whether a package passes inspection before it goes out. Short concrete asks work better than long sentences.

### Does connecting Appian give the AI every environment and every package?

No. Access follows the person who signed in to Elaichi, and an Appian connection only reaches what the API key behind it is allowed to reach. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one Appian connection?

Yes. One person connects Appian with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so every deployment or inspection in the log names the person who asked for it.

### Can I stop an agent from creating deployments in Appian?

Yes. Restrictions in Elaichi work per action, so you can restrict creating a deployment or an inspection in Appian for a role or for one person while leaving the listing and log actions open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Appian connection when someone leaves?

Offboarding that person in Elaichi ends their access to Appian at once, from every client they used. A shared Appian connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the Appian MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Appian is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Appian?

Yes. Both let Claude, ChatGPT or Cursor use Appian. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Appian call.

### How is Elaichi different from Composio for Appian?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Appian: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 8 Appian tools

Every tool below is callable through https://api.elaichi.ai/mcp once Appian is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Appian deployment** (Create). Start an Appian deployment: export an application or package(s) (truto_action_type=export) or deploy (import) a package into this environment (truto_action_type=import). Runs asynchronously; poll deployments.list with the returned uuid. Export needs outgoing deployments enabled, import needs incoming; otherwise Appian returns 403. Import requires uploading .zip/.properties files as extra multipart parts, which MCP clients cannot send. Required: truto_action_type, json.
- **List all Appian deployments** (List). Get the status and results of an export or import deployment. Status is one of IN_PROGRESS, PENDING_REVIEW, COMPLETED, COMPLETED_AND_SYNCING, COMPLETED_WITH_IMPORT_ERRORS, COMPLETED_WITH_PUBLISH_ERRORS, COMPLETED_WITH_EXPORT_ERRORS, FAILED, REJECTED or UNAVAILABLE. Finished exports include download URLs for the package zip, database scripts, plug-ins and customization files; imports include object, plug-in, admin console setting and database script counts. Required: deployment_id.
- **Get single Appian deployment log by ID** (Get). Get the plain-text log of a deployment (export or import). Required: id.
- **Create a Appian inspection** (Create). Inspect a package, admin console settings file or import customization file before deploying, to find missing precedents and errors. Runs asynchronously; poll inspections.list with the returned uuid. Requires uploading files as extra multipart parts, which MCP clients cannot send. Required: json.
- **List all Appian inspections** (List). Get inspection results: expected object and admin console setting counts, and the errors and warnings that would occur on deployment. Status is IN_PROGRESS, COMPLETED or FAILED (system error only). Required: inspection_id.
- **List all Appian application packages** (List). List the in-flight packages of an Appian application (up to 500, newest first), to find a package UUID to export. Available in API v2 and v3. Required: application_uuid.
- **List all Appian releases** (List). List releases (Appian 26.8+, API v3), with name, target date, owner and package count. Read-only.
- **Get single Appian release by ID** (Get). Get a release and all of its packages across applications (Appian 26.8+, API v3). Required: id.
