How do I find my Airship App Key and Master Secret?

Log in to the Airship dashboard, go to **Settings** > **APIs & Integrations**, and select **Tokens**. You will find your App Key and can generate/view your Master Secret there.

Which region should I choose?

Choose **US** if your project is hosted on `go.urbanairship.com` or **EU** if it is hosted on `go.airship.eu`. Using the wrong region will result in authentication failures.

Can I target specific users by their email?

Yes! Use the `send_push_notification` tool and specify the `named_user` in the audience. If your user's email is mapped as their Named User ID, Airship will deliver the push to all their associated devices.

Airship MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Airship
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Airship through Vinkius, pass the Edge URL in the `mcps` parameter and every Airship tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Airship Specialist",
    goal="Help users interact with Airship effectively",
    backstory=(
        "You are an expert at leveraging Airship tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Airship "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Airship MCP Server

Connect your Airship (formerly Urban Airship) account to your AI agent to unlock professional mobile and web engagement orchestration. From sending targeted push notifications to auditing subscriber segments and managing named user associations across multiple channels, your agent handles your multi-channel communication strategy through natural conversation.

When paired with CrewAI, Airship becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Airship tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Push Orchestration — Send and monitor push notifications to specific audiences, segments, or all users
Segmentation Oversight — List and retrieve criteria for your audience segments, including tags and attributes
Channel Management — List and audit communication channels (iOS, Android, Web, Email) and retrieve technical metadata
User Association — Manage named users to map multiple devices and channels to a single customer profile
Engagement Insights — Quickly identify active segments or audit delivery statuses directly from your chat interface

The Airship MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Airship to CrewAI via MCP

Follow these steps to integrate the Airship MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Airship

Why Use CrewAI with the Airship MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Airship through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Airship + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Airship MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Airship for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Airship, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Airship tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Airship against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Airship MCP Tools for CrewAI (10)

These 10 tools become available when you connect Airship to CrewAI via MCP:

associate_named_user

Link device to user

get_channel_details

Get device metadata

get_push_status

Check push delivery

get_segment_details

Get segment criteria

list_channels

List app channels

list_named_users

List named users

list_segments

List audience segments

list_static_lists

g. CSV uploads) in your account. List static audiences

list_tags

List audience tags

send_push_notification

Send a push alert

Example Prompts for Airship in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Airship immediately.

"Send a push notification to all users with alert 'Big Sale starting now!'."

"List all audience segments in my EU project."

"Show details for channel ID '12345678-90ab-cdef-1234-567890abcdef'."

Troubleshooting Airship MCP Server with CrewAI

Common issues when connecting Airship to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Airship + CrewAI FAQ

Common questions about integrating Airship MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.