Bring Parcel Tracking
to CrewAI
Learn how to connect Ship24 to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Ship24 MCP Server?
Connect your Ship24 account to any AI agent and take full control of your global logistics tracking and parcel orchestration through natural conversation. Ship24 provides a premier multi-carrier tracking API, and this integration allows you to create trackers, monitor real-time delivery progress, and search through thousands of couriers directly from your chat interface.
What you can do
- Parcel & Tracking Orchestration — Create and manage parcel trackers programmatically to keep your delivery pipeline synchronized.
- Real-time Status Intelligence — Retrieve detailed tracking results for specific trackers, including milestones and location history directly from the AI interface.
- Synchronous Tracking Control — Perform instant tracking lookups for any tracking number and courier code using simple AI commands.
- Courier & Logistics Discovery — List and search through thousands of supported couriers to find the correct tracking provider via natural language.
- Operational Monitoring — Track system health and manage bulk trackers to ensure your logistics orchestration is always optimized.
How it works
1. Subscribe to this server
2. Enter your Ship24 API Key from your dashboard
3. Start managing your global parcel tracking from Claude, Cursor, or any MCP-compatible client
No more wrestling with multiple carrier websites to find your packages. Your AI acts as a dedicated logistics coordinator or customer support assistant.
Who is this for?
- Logistics Managers — quickly retrieve parcel statuses and monitor courier performance without switching sites.
- Customer Success Teams — automate the retrieval of tracking details for client inquiries via natural conversation.
- Growth Engineers — integrate multi-carrier tracking capabilities into custom AI-driven supply chain workflows.
Built-in capabilities (12)
Bulk start tracking
Start tracking package
Stop tracking package
Lookup by tracking number
Get API connectivity
Live package update
Get package status
List all trackers
List bulk shipments
List supported carriers
g. FedEx, Correios). Find carrier codes
Update tracker metadata
Why CrewAI?
When paired with CrewAI, Ship24 becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Ship24 tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Ship24 in CrewAI
Ship24 and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Ship24 to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Ship24 in CrewAI
The Ship24 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Ship24 for CrewAI
Every tool call from CrewAI to the Ship24 MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the tracking status of a specific package just by providing the tracking number?
Yes! Use the get_live_tracking tool with the tracking number. Your agent will respond with the real-time status, carrier info, and current location in seconds.
How do I search for a specific carrier code (e.g. FedEx or DHL)?
Simply ask the agent to run the search_couriers action with the name of the carrier. It will retrieve the correct identifier for that provider.
How do I find my Ship24 API Key?
Log in to your Ship24 account, navigate to the Dashboard, and select API to copy your unique secret API key.
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.
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.