# Accelerate with AI
Use Airship's AI tools to interact with the platform through natural language to send pushes, manage channels, automate workflows, and implement mobile SDK features.
# AI tools for Airship developers
> Use Airship's developer AI tools with coding assistants to work with the platform through natural language. You get live access to APIs and documentation resources, plus structured workflows for implementation tasks that build on that access where supported. {{< badge "ai" "Agentic AI" >}}
Airship publishes two complementary options for developers who want to work with the platform from AI assistants: a library of skills and an MCP server. They suit tasks from quick API calls to long implementation projects but address different layers of the stack.
* **Skills** — A skill is a portable bundle of instructions that steers an AI assistant through a task the same way every time. Airship Skills follow the open Agent Skills standard. Individual skills are focused operations you can use alone or as part of a workflow. Workflows are multi-step processes that interpret responses and adapt.
* **MCP server** — [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard for connecting assistants to external tools and data. The Airship MCP server gives MCP-compatible clients authenticated, real-time access to Airship APIs, documentation, and SDK migration guidance.
In supported setups, Skills are designed to run on top of MCP. The server supplies the live Airship connection and tool surface, and Skills supply the structured playbooks, from editing code to validating behavior. Assistants that support Agent Skills can also load skills directly without MCP, depending on how you configure your environment.
See also [AI in Airship](https://www.airship.com/docs/guides/features/intelligence-ai/ai/).
> **Important:** **Additional Terms and Disclaimer**
> Airship Agent Tools, including the Airship MCP server and Airship Skills, are open-source tools provided by Airship "as is" and without any warranties. Use of these tools is at your own risk and subject to the [Terms of Subscription Service](https://www.airship.com/legal/subscription-terms/) or other applicable Agreement entered into with Airship governing for use of the Airship Service and the [Acceptable Use Policy](https://www.airship.com/legal/acceptable-use/).
>
> [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) and the [Agent Skills standard](https://agentskills.io/) are open-source protocols maintained by third parties. These protocols are evolving and may be susceptible to security issues or vulnerabilities. Airship does not control and makes no warranties regarding these protocols.
>
> **AI Assistant Outputs**
> AI assistants connected through these tools may produce inaccurate, incomplete, or unexpected results. You are responsible for reviewing all outputs and testing actions in a non-production environment before deploying to live audiences. Airship is not responsible for any consequences arising from actions taken based on AI assistant outputs.
>
> **Data Processed by Third-Party AI Assistants**
> When you use these tools with a third-party AI assistant, such as Claude, Cursor, or Windsurf, both your prompts and Airship API responses are processed by your AI assistant provider. API responses may include end-user personal data such as email addresses, phone numbers, device identifiers, named user IDs, tags, and attributes. Airship does not control and is not responsible for how your AI assistant provider processes this data. Before connecting these tools to an AI assistant, verify that your AI assistant provider's data processing practices are compatible with your obligations under applicable data protection laws and your organization's privacy policies.
>
> **Credentials and Security**
> You are responsible for securing your OAuth 2.0 credentials. Do not share credentials, commit them to version control, or expose them in prompts or public repositories. Airship is not responsible for any consequences arising from compromised, misconfigured, or overly permissive credentials.
>
> **Open-Source Modifications**
> These tools are open-source. If you modify, fork, or extend them, Airship is not responsible for any issues arising from such modifications.
>
> For assistance, [contact Airship Support](https://support.airship.com/).
# Airship Skills
> Use Airship Skills with your AI assistant to automate and implement Airship platform tasks. {{< badge "ai" "Agentic AI" >}}
A skill is a portable set of instructions that teaches your AI assistant how to complete a specific kind of task in a consistent, repeatable way. Airship Skills work with Claude Code, Cursor, Windsurf, and other assistants that use the open Agent Skills standard.
## Why use Airship Skills
Airship Skills teach AI assistants to handle Airship tasks, from targeted REST API operations, such as registering a channel, sending a push, or creating an automation pipeline, to guided mobile SDK implementation workflows that detect your platform, write code, and verify the result.
Using Skills gives you these benefits:
- **Time savings** — Pre-built Skills speed up implementation.
- **Accuracy** — Workflows catch errors and adapt as needed.
- **Consistency** — Assistants follow the same process every time.
- **Speed** — Multi-step tasks run automatically, no micromanagement needed.
## Organization
Skills are organized in two layers:
* **Workflows** are the primary entry point for most tasks. A workflow chains multiple operations into an end-to-end process, interpreting results and dynamically adjusting. For example, an onboarding workflow registers email and SMS channels, associates them with a named user, records a custom event, and sends a welcome notification. Each step is informed by the previous one's output.
* **Individual skills** are the fundamental actions used within workflows, but you can also run them independently for targeted tasks. While a workflow chains multiple skills together for complex processes, an individual skill might simply look up a channel, send a push notification, or update a Wallet pass.
## Workflow examples
Workflows available in Airship Skills include:
- Registering and associating an email or SMS channel with a [Named User](https://www.airship.com/docs/reference/glossary/#named_user)
- Creating automations triggered by [Custom Events](https://www.airship.com/docs/reference/glossary/#custom_event), with personalized messaging using [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars) templates
- Discovering existing automations and generating sample events that would trigger them
- Exporting an entire audience using parallel pagination across UUID prefixes
- Monitoring [Real-Time Data Streaming](https://www.airship.com/docs/reference/glossary/#rtds) event streams with automatic reconnection
- Updating Wallet passes in response to events from a point-of-sale system
## Get Airship Skills
Browse the Airship AI Tools repository to see what's available or clone it to inspect skill definitions locally: https://github.com/urbanairship/agent-tools.
> **Important:** **Additional Terms and Disclaimer**
> Airship Agent Tools, including the Airship MCP server and Airship Skills, are open-source tools provided by Airship "as is" and without any warranties. Use of these tools is at your own risk and subject to the [Terms of Subscription Service](https://www.airship.com/legal/subscription-terms/) or other applicable Agreement entered into with Airship governing for use of the Airship Service and the [Acceptable Use Policy](https://www.airship.com/legal/acceptable-use/).
>
> [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) and the [Agent Skills standard](https://agentskills.io/) are open-source protocols maintained by third parties. These protocols are evolving and may be susceptible to security issues or vulnerabilities. Airship does not control and makes no warranties regarding these protocols.
>
> **AI Assistant Outputs**
> AI assistants connected through these tools may produce inaccurate, incomplete, or unexpected results. You are responsible for reviewing all outputs and testing actions in a non-production environment before deploying to live audiences. Airship is not responsible for any consequences arising from actions taken based on AI assistant outputs.
>
> **Data Processed by Third-Party AI Assistants**
> When you use these tools with a third-party AI assistant, such as Claude, Cursor, or Windsurf, both your prompts and Airship API responses are processed by your AI assistant provider. API responses may include end-user personal data such as email addresses, phone numbers, device identifiers, named user IDs, tags, and attributes. Airship does not control and is not responsible for how your AI assistant provider processes this data. Before connecting these tools to an AI assistant, verify that your AI assistant provider's data processing practices are compatible with your obligations under applicable data protection laws and your organization's privacy policies.
>
> **Credentials and Security**
> You are responsible for securing your OAuth 2.0 credentials. Do not share credentials, commit them to version control, or expose them in prompts or public repositories. Airship is not responsible for any consequences arising from compromised, misconfigured, or overly permissive credentials.
>
> **Open-Source Modifications**
> These tools are open-source. If you modify, fork, or extend them, Airship is not responsible for any issues arising from such modifications.
>
> For assistance, [contact Airship Support](https://support.airship.com/).
# Airship MCP Server
> Learn about the Airship MCP server, which lets you interact with Airship features through natural language using AI-powered tools. {{< badge "ai" "Agentic AI" >}}
[Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard that allows AI assistants to securely connect to external tools and data sources. The Airship MCP server works with Claude Code, Claude Desktop, Cursor, and other MCP-compatible clients.
## Why use the Airship MCP server
The Airship MCP server is a development tool for building and maintaining Airship integrations. It connects AI assistants to the Airship platform in real time, so you can query channel data, test push flows, and migrate SDKs without leaving your editor.
If you spend time switching between Airship documentation, the dashboard, and your codebase, the MCP server brings those workflows into a single conversation. Common use cases include the following:
- **Migrating SDKs** — Start a guided migration that detects your current platform and version, then walks you through each required change with rollback support.
- **Testing push notifications** — Send pushes to tags, channels, or Named Users and validate payloads during development.
- **Looking up channels and audiences** — Inspect tags, [Attributes](https://www.airship.com/docs/reference/glossary/#attributes), opt-in status, and audience [Segments](https://www.airship.com/docs/reference/glossary/#segment) without opening the dashboard.
- **Running multi-step workflows** — Use [Skills](https://www.airship.com/docs/developer/ai-tools/skills/) to complete tasks like registering email or SMS channels, managing Named Users, or configuring Message Center. The process is guided start to finish by your assistant.
- **Pulling documentation into context** — Ask for setup guides, API specs, or SDK references and get them inline, right where you're working.
You interact with the server through natural-language prompts. For example, your conversation can include prompts like "Send a test push to all users tagged beta_testers" or "Look up channel 9c6b3b5e-1234-5678-abcd-ef0123456789 and show me its opt-in status".
> **Important:** **Additional Terms and Disclaimer**
> Airship Agent Tools, including the Airship MCP server and Airship Skills, are open-source tools provided by Airship "as is" and without any warranties. Use of these tools is at your own risk and subject to the [Terms of Subscription Service](https://www.airship.com/legal/subscription-terms/) or other applicable Agreement entered into with Airship governing for use of the Airship Service and the [Acceptable Use Policy](https://www.airship.com/legal/acceptable-use/).
>
> [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) and the [Agent Skills standard](https://agentskills.io/) are open-source protocols maintained by third parties. These protocols are evolving and may be susceptible to security issues or vulnerabilities. Airship does not control and makes no warranties regarding these protocols.
>
> **AI Assistant Outputs**
> AI assistants connected through these tools may produce inaccurate, incomplete, or unexpected results. You are responsible for reviewing all outputs and testing actions in a non-production environment before deploying to live audiences. Airship is not responsible for any consequences arising from actions taken based on AI assistant outputs.
>
> **Data Processed by Third-Party AI Assistants**
> When you use these tools with a third-party AI assistant, such as Claude, Cursor, or Windsurf, both your prompts and Airship API responses are processed by your AI assistant provider. API responses may include end-user personal data such as email addresses, phone numbers, device identifiers, named user IDs, tags, and attributes. Airship does not control and is not responsible for how your AI assistant provider processes this data. Before connecting these tools to an AI assistant, verify that your AI assistant provider's data processing practices are compatible with your obligations under applicable data protection laws and your organization's privacy policies.
>
> **Credentials and Security**
> You are responsible for securing your OAuth 2.0 credentials. Do not share credentials, commit them to version control, or expose them in prompts or public repositories. Airship is not responsible for any consequences arising from compromised, misconfigured, or overly permissive credentials.
>
> **Open-Source Modifications**
> These tools are open-source. If you modify, fork, or extend them, Airship is not responsible for any issues arising from such modifications.
>
> For assistance, [contact Airship Support](https://support.airship.com/).
## Set up the server
Follow these steps to set up the Airship MCP server with your MCP-compatible client. You'll need a terminal app to run commands and install tooling.
### Get your project credentials
The Airship MCP server authenticates with [OAuth 2.0](https://www.airship.com/docs/guides/getting-started/developers/api-security/#oauth-20) client credentials. You need your project's [App Key](https://www.airship.com/docs/reference/glossary/#app_key), an OAuth Client ID, and a Client Secret. All are available from the [Airship dashboard](https://go.airship.com/).
First, get your app key:
*Viewing your project details*
1. Open your project.
1. Select the dropdown menu () next to your project name, and then **Project details**.
1. Copy your app key and close the modal window.
Next, create OAuth client credentials by following the steps in [Create client credentials](https://www.airship.com/docs/guides/getting-started/developers/api-security/#create-client-credentials) in *Airship API Security*. When creating your credentials:
- 
*Allowing basic auth in OAuth configuration*
Enable **Allow Basic Auth** to generate a Client Secret. The MCP server requires a Client Secret to authenticate with the token endpoint.
- 
*Enabling scopes in OAuth configuration*
Enable the **Push**, **Channels**, and **Named Users** scopes at minimum. Enable additional scopes to match the tools you plan to use.
Copy the Client ID and Client Secret after saving. The Client Secret is only shown once.
> **Important:** Keep your Client Secret secure. Do not share it or commit it to version control. The MCP server uses these credentials to send push notifications and access channel data on your behalf.
### Install uv
Install uv, a command-line tool by [Astral](https://astral.sh/) for Python package management:
#### macOS / Linux
```bash
curl -LsSf https://astral.sh/uv/install.sh | sh
```
The output is similar to the following:
```text
downloading uv 0.8.9 aarch64-apple-darwin
no checksums to verify
installing to /Users/yourname/.local/bin
uv
uvx
everything's installed!
```
#### Windows
Open PowerShell and run:
```powershell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
```
### Download the MCP server
Clone the Airship MCP server repository to your local machine:
```bash
git clone https://github.com/urbanairship/agent-tools.git
cd agent-tools
```
### Configure your MCP client
Follow these steps to configure your MCP client:
#### Claude Desktop
1. Go to **Settings**, then **Developer**, then **Edit Config**.
1. Add the Airship MCP server to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"airship-mcp": {
"command": "uv",
"args": ["run", "--directory", "/path/to/agent-tools", "airship-mcp"],
"env": {
"AIRSHIP_APP_KEY": "your_app_key",
"AIRSHIP_CLIENT_ID": "your_client_id",
"AIRSHIP_CLIENT_SECRET": "your_client_secret",
"AIRSHIP_REGION": "us"
}
}
}
}
```
1. Replace `/path/to/agent-tools` with the path to the cloned repository.
1. Replace `your_app_key`, `your_client_id`, and `your_client_secret` with your [Airship credentials](#get-your-project-credentials).
1. For `AIRSHIP_REGION`, use the appropriate value of `us` or `eu`.
1. Save the file and restart Claude Desktop.
#### Cursor
1. In your project, create or edit `.cursor/mcp.json` (or `~/.cursor/mcp.json` for global configuration):
```json
{
"mcpServers": {
"airship-mcp": {
"command": "uv",
"args": ["run", "--directory", "/path/to/agent-tools", "airship-mcp"],
"env": {
"AIRSHIP_APP_KEY": "your_app_key",
"AIRSHIP_CLIENT_ID": "your_client_id",
"AIRSHIP_CLIENT_SECRET": "your_client_secret",
"AIRSHIP_REGION": "us"
}
}
}
}
```
1. Replace `/path/to/agent-tools` with the path to the cloned repository.
1. Replace `your_app_key`, `your_client_id`, and `your_client_secret` with your [Airship credentials](#get-your-project-credentials).
1. For `AIRSHIP_REGION`, use the appropriate value of `us` or `eu`.
1. Restart Cursor or reload the window.
#### Other MCP clients
For other MCP-compatible clients, refer to the client's documentation for specific instructions. Use the following values in your configuration:
- **Command**: `uv`
- **Arguments**: `["run", "--directory", "/path/to/agent-tools", "airship-mcp"]`
- **Environment variables**:
- `AIRSHIP_APP_KEY`: Your app key
- `AIRSHIP_CLIENT_ID` and `AIRSHIP_CLIENT_SECRET`: Your OAuth [client credentials](#get-your-project-credentials)
- `AIRSHIP_REGION`: `us` or `eu`
#### Claude Code
After cloning the repository, install it as a Claude Code plugin:
```bash
claude plugin marketplace add /path/to/agent-tools
claude plugin install airship
```
Skills are available as `/airship:` slash commands. The `airship-mcp` server starts automatically, no JSON config needed.
To persist credentials across sessions, add them to your shell profile as environment variables:
```bash
export AIRSHIP_APP_KEY=your_app_key
export AIRSHIP_CLIENT_ID=your_client_id
export AIRSHIP_CLIENT_SECRET=your_client_secret
export AIRSHIP_REGION=us
```
Replace `your_app_key`, `your_client_id`, and `your_client_secret` with your [Airship credentials](#get-your-project-credentials). For `AIRSHIP_REGION`, use the appropriate value of `us` or `eu`.
### Verify the connection
First, confirm the server is connected by asking your assistant what Airship tools are available:
#### Claude Desktop
1. Open a new conversation.
1. Look for the hammer icon (🔨) indicating MCP tools are available.
1. Ask "What Airship tools are available?"
Claude should respond with a list of available tools.
#### Cursor
1. Start a new chat.
1. Ask "What Airship tools are available?"
The assistant should respond with a list of available tools.
#### Claude Code
Ask "What Airship tools are available?" or run a Skill to confirm the connection:
```text
/airship:push-notification
```
Claude should respond with a list of available tools.
Next, try sending a push notification to a device registered with the `test` tag or a different tag in your project:
```text
Send a test push notification to the tag "test" with the message "Hello from MCP!"
```
### Install Skills
The Airship MCP server includes [Skills](https://www.airship.com/docs/developer/ai-tools/skills/), which are optional to install. To install them, ask the AI assistant:
```text
Install the Airship Skills for this project
```
When prompted, provide the path to your project directory. To update Skills to the latest version:
```text
Update my Airship Skills
```
## Capabilities and usage
The Airship MCP server provides tools and resources that AI assistants can use to help with development tasks. The following sections describe some common uses with example prompts.
And you can always ask your assistant for a list of options:
```text
What can the Airship MCP tool help me with?
```
### SDK migration
Start a guided migration with automatic version and platform detection:
```text
Help me migrate my Airship SDK to the latest version
```
The assistant asks for your project path, detects the platform and current version, then walks you through each required change.
You can also specify parameters directly:
```text
Migrate my iOS project at /Users/me/MyApp from SDK 19.0.0 to 20.0.0
```
### Push notifications
Send push notifications to tags, channels, or Named Users, and validate payloads before sending to real users:
```text
Send a push notification to all users with the "beta_testers" tag, with the message "New feature available"
```
> **Important:** Always test using a dedicated tag or channel before sending to broad audiences.
### Channel and audience tools
Look up channels and Named Users, inspect tags and [Attributes](https://www.airship.com/docs/reference/glossary/#attributes), and manage audience [Segments](https://www.airship.com/docs/reference/glossary/#segment):
```text
Look up channel 9c6b3b5e-1234-5678-abcd-ef0123456789 and show me its tags
```
### Skills
If you [installed Skills](#install-skills), you can run them directly from your chat or agent panel:
```text
Register email user@example.com and associate it with named user "user123"
```
See [Skills](https://www.airship.com/docs/developer/ai-tools/skills/) for more information.
### Documentation
Ask the assistant to look up documentation on any topic:
```text
Show me the spec for updating an iOS badge
```