Bring Last Mile Delivery
to CrewAI
Learn how to connect Shipday to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Shipday MCP Server?
Connect your Shipday account to any AI agent and take full control of your last-mile delivery and dispatch orchestration through natural conversation. Shipday provides a premier platform for managing local delivery operations, and this integration allows you to retrieve order metadata, assign drivers, and track delivery progress directly from your chat interface.
What you can do
- Order & Dispatch Orchestration — List all managed delivery orders and retrieve detailed metadata, including status and customer info programmatically.
- Driver Lifecycle Management — Access and monitor your driver directory and assign drivers to specific orders directly from the AI interface.
- Delivery Progress Intelligence — Retrieve real-time tracking progress for active orders to keep your customers informed via natural language.
- Status Lifecycle Control — Update order statuses and monitor carrier metadata to ensure your delivery pipeline is always synchronized.
- Operational Monitoring — Track system activity and monitor order fulfillment to ensure reliable last-mile orchestration using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Shipday API Key from your dashboard settings
3. Start managing your local deliveries from Claude, Cursor, or any MCP-compatible client
No more juggling multiple delivery tabs to coordinate your fleet. Your AI acts as a dedicated dispatcher or delivery operations manager.
Who is this for?
- Restaurant & Retail Managers — quickly dispatch orders and monitor driver availability without switching apps.
- Delivery Operations Teams — automate the assignment of drivers and track order progress via natural conversation.
- Customer Support Teams — streamline the retrieval of delivery status and monitor fulfillment directly within the chat.
Built-in capabilities (9)
Assign an order to a driver
Provide orderNumber, customer details, and restaurant info. Create a new delivery order
Delete/Cancel an order
Get details for a carrier order
Get details of a specific order
Get real-time tracking for a delivery
List all active delivery orders
List all drivers
Update the status of an order
Why CrewAI?
When paired with CrewAI, Shipday becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Shipday 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
Shipday in CrewAI
Shipday and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Shipday 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 Shipday in CrewAI
The Shipday 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 9 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
Shipday for CrewAI
Every tool call from CrewAI to the Shipday 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 status of a delivery order just by providing its ID?
Yes! Use the get_order tool with the Order ID. Your agent will respond with the current status, customer details, and scheduled delivery times in seconds.
How do I assign a specific driver to an active order?
Simply ask the agent to run the assign_driver action. You will need to provide both the Order ID and the Driver ID to complete the assignment.
How do I find my Shipday API Key?
Log in to your Shipday dashboard, navigate to Settings > API, and you will find your unique secret API key there.
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.