How do I get an AfterShip API Key?

Sign up at [**AfterShip**](https://www.aftership.com/), go to Settings > API Keys, and generate a new key. Free tier includes 100 shipments/month.

How many couriers are supported?

AfterShip supports 1,000+ courier companies worldwide including FedEx, UPS, DHL, USPS, Royal Mail, Canada Post, Australia Post, and many regional carriers.

Can I automatically detect which courier handles my tracking number?

Yes! Use the `detect_courier` tool with just the tracking number. It returns a ranked list of likely courier companies based on the tracking number format.

AfterShip MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: AfterShip
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to AfterShip through Vinkius, pass the Edge URL in the `mcps` parameter and every AfterShip 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="AfterShip Specialist",
    goal="Help users interact with AfterShip effectively",
    backstory=(
        "You are an expert at leveraging AfterShip 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 AfterShip "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 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 AfterShip MCP Server

Connect AfterShip tracking platform to any AI agent and track packages from 1,000+ couriers worldwide, auto-detect shipping companies, and manage all your shipments through natural language.

When paired with CrewAI, AfterShip becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AfterShip 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

Package Tracking — Create and monitor shipments from FedEx, UPS, DHL, USPS, and 1,000+ other couriers
Auto-Detect Courier — Automatically identify the shipping company from just a tracking number
Tracking History — View complete delivery history with checkpoint timestamps and locations
Delivery Management — Mark trackings as completed, retrack expired ones, or delete old entries
Customer Notifications — Set up email and SMS notifications for delivery updates
Courier Directory — Browse all supported courier companies with their contact info and requirements

The AfterShip MCP Server exposes 9 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 AfterShip to CrewAI via MCP

Follow these steps to integrate the AfterShip 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 9 tools from AfterShip

Why Use CrewAI with the AfterShip MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AfterShip 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

AfterShip + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries AfterShip 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 AfterShip, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AfterShip 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 AfterShip against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AfterShip MCP Tools for CrewAI (9)

These 9 tools become available when you connect AfterShip to CrewAI via MCP:

create_tracking

Requires at least the tracking number. Optionally specify the courier slug, title, customer emails, SMS phone numbers, order ID, and custom fields. Create a new package tracking

delete_tracking

This action cannot be undone. Delete a tracking entry

detect_courier

Useful when the user provides a tracking number but doesn't know which courier it belongs to. Returns a ranked list of likely couriers. Auto-detect courier from tracking number

get_tracking

Get details of a specific tracking

list_couriers

) that can be used for tracking packages. List all supported courier companies

list_trackings

Supports extensive filtering by courier (slug), tag, keyword, origin, destination, date ranges, and delivery status. List all package trackings

mark_tracking_completed

Useful when the package has been delivered but the courier hasn't updated the final status. Mark a tracking as completed

retrack_tracking

This restarts monitoring and will fetch new checkpoint updates. Retrack an expired tracking

update_tracking

Does not affect the tracking number or courier. Update an existing tracking

Example Prompts for AfterShip in CrewAI

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

"Track my package with tracking number 1Z999AA10123456784."

"What courier handles tracking number 9400111899223344556677?"

"Show me all my active trackings."

Troubleshooting AfterShip MCP Server with CrewAI

Common issues when connecting AfterShip 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.

AfterShip + CrewAI FAQ

Common questions about integrating AfterShip 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.