Bring Wms
to CrewAI
Learn how to connect ShipHero to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the ShipHero MCP Server?
Connect your ShipHero account to any AI agent to streamline your warehouse and fulfillment operations through natural language.
What you can do
- Order Management — List recent orders and create new ones with full shipping and line item details.
- Inventory Control — Check real-time stock levels by SKU, track history of inventory changes, and add or remove stock instantly.
- Bulk Operations — Sync inventory levels in bulk using CSV URLs for rapid warehouse updates.
- Product Insights — Retrieve deep metadata for products, including warehouse-specific availability and legacy ID conversion.
- Automation — Register webhooks to stay updated on inventory changes or order statuses.
How it works
- Subscribe to this server
- Enter your ShipHero Access Token
- Start managing your logistics from Claude, Cursor, or any MCP-compatible client
Who is this for?
- E-commerce Managers — monitor fulfillment health and stock levels without leaving your workspace
- Operations Teams — quickly adjust inventory and track movement history during audits
- Developers — integrate warehouse data into your workflow and test webhooks via simple prompts
Built-in capabilities (8)
Add or remove inventory for a SKU
Create a new order in ShipHero
Register a new webhook
Get product details by SKU
Get UUID from a legacy numeric ID
List inventory changes for a SKU
List ShipHero orders
Bulk sync inventory via CSV URL
Why CrewAI?
When paired with CrewAI, ShipHero becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ShipHero 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
ShipHero in CrewAI
ShipHero and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ShipHero 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 | 4,000+ 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 ShipHero in CrewAI
The ShipHero 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 8 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
ShipHero for CrewAI
Every tool call from CrewAI to the ShipHero MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I track the history of stock movements for a specific product?
You can use the list_inventory_changes tool by providing the product SKU. It will return a detailed history of inventory adjustments, helping you audit stock movements over time.
Is it possible to bulk update inventory levels across my warehouse?
Yes! The sync_inventory tool allows you to provide a URL to a CSV file containing your inventory data. The server will process the file and sync the levels for the specified warehouse ID.
What should I do if I only have a legacy numeric ID for an order or product?
Use the get_uuid tool. It is specifically designed to convert legacy numeric IDs into the opaque UUIDs required by the modern ShipHero API for entities like Orders or Products.
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.
Explore More MCP Servers
View all →
Uniphore Conversation AI
8 toolsAccess meeting transcripts, summaries, action items, and analytics via Uniphore API.
OOPSpam
12 toolsBlock spam submissions on your forms and comments with an AI-powered filter that catches bots without annoying real users.
MonkeyLearn
10 toolsAnalyze and extract data from text via MonkeyLearn — sentiment analysis and keyword extraction directly from your AI agent.
LeadSquared
10 toolsManage leads, sales activities, and opportunities via the LeadSquared CRM API.