ShippingBo MCP for AI. Manage orders, inventory, and shipments from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
ShippingBo MCP Server manages all your e-commerce logistics, from order placement to final delivery. It centralizes fulfillment by connecting directly to multi-warehouse stock levels and carrier networks used by French retailers.
Your AI agent handles everything: listing orders, checking product inventory status, updating stock counts, and tracking shipments—all without you leaving the chat window.
What your AI can do
Get order
Pulls specific details about one single order using its ID.
Get product
Retrieves the full data sheet for a specified product SKU.
List orders
Generates an aggregated list of all placed orders in the system.
Retrieves specific metadata for a single sales order.
Generates a complete list of all current and past orders in the system.
Changes the available stock level for any given product ID.
Retrieves comprehensive information about a specific product SKU.
Pulls the complete catalog listing for every item you sell.
Lists existing shipments and provides real-time tracking updates on delivery status.
Maps out the available physical storage locations within your warehouse.
Ask an AI about this
Waiting for input…
ShippingBo MCP Server: 8 Tools for Logistics Ops
Coordinate order details, product data, shipment tracking, and inventory levels across all your e-commerce operations.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ShippingBo on VinkiusGet Order
Pulls specific details about one single order using its ID.
Get Product
Retrieves the full data sheet for a specified product SKU.
List Orders
Generates an aggregated list of all placed orders in the system.
List Packs
Lists available packaging materials and options for shipments.
List Products
Gets a complete list of every product SKU sold through the platform.
List Shipments
Retrieves tracking and status data for multiple outgoing shipments.
List Warehouse Slots
Displays a map of all available physical storage slots in the warehouse.
Update Stock
Changes the active stock count for any product ID, reflecting inventory changes.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The ShippingBo integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ShippingBo, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ShippingBo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking an order shouldn't require jumping between four different websites.
Today, figuring out where a customer's package is requires a painful process. You log into the main CRM to get the Order ID. Then you copy that ID and paste it into the carrier portal (FedEx). If FedEx doesn't have it, you try the second carrier (UPS), copying the tracking number again. This whole sequence takes three minutes of manual clicking and copy/pasting.
With this MCP server, your agent handles all those hops for you. You tell it, 'What is the status of order 987?' The agent uses `list_shipments`, aggregates data from multiple carriers behind the scenes, and reports back: 'It's currently in transit via Carrier B; expected delivery tomorrow.' It’s one question, one answer.
ShippingBo MCP Server: Get accurate inventory updates with `update_stock`.
Manual stock adjustments are a nightmare. A team member counts 10 boxes of product and needs to update the system, but they have to find the SKU, navigate to the WMS module, enter the new number, and save—all while juggling other tasks.
Now? You just tell your agent: 'Set stock for Product Z to 85.' The tool runs `update_stock` directly. It's immediate, verifiable, and means your system counts match reality every time.
What your AI can actually do with this
Listen up. This ShippingBo MCP Server runs your whole e-commerce operation through your AI client. Forget juggling dashboards; you connect this server and let your agent handle everything from the moment an order hits the system until it's actually in a customer’s hands. It connects directly to multi-warehouse stock levels and carrier networks used by French retailers, so you don't have to worry about geographical headaches.
Your AI client handles the whole loop: listing orders, checking inventory, updating counts, and tracking shipments—all from your chat window.
Handling Orders & Catalog Data
When it comes to order flow, you've got two ways to pull data. If you know the specific ID of an order, run get_order and you'll get all the metadata for that single transaction. But if you need a full picture—the whole backlog—you just call list_orders. That generates an aggregated list of every current and past order in your system.
For product info, you can pull the complete data sheet for one item using get_product with its SKU, or grab the entire catalog listing by running list_products. If you need to know what packaging materials are available for a shipment, just check out list_packs.
Inventory and Stock Control
Managing stock is where this thing shines. You can view every product SKU sold on the platform using list_products, which gives you the master list. If an item's count changes—say, a shipment gets lost or you get a bulk return—you don't have to manually update anything; you use update_stock and pass the new count for any product ID, making sure your records match reality immediately.
You can also check physical storage capacity by running list_warehouse_slots, which maps out every available slot in your warehouse.
Shipment Tracking & Fulfillment
Shipping is a process that needs eyes on it constantly. To get a comprehensive overview of everything going out the door, you use list_shipments. This pulls real-time tracking and status data for multiple outgoing shipments at once. If you need to know exactly what slots are available before staging goods, you run list_warehouse_slots again; this shows a map of physical storage locations.
Because all these tools are grouped together, your agent can process a sequence: first, it checks get_order for the details on Order 1234; then, it uses get_product to confirm that SKU XYZ is still in stock; next, it calls list_warehouse_slots to find an empty spot; and finally, it triggers update_stock if needed.
It's one conversation, all the data you need.
How Your Agent Uses This
Your AI agent doesn't just read a list of functions—it knows how they talk to each other. You tell it, 'I gotta ship Order 500,' and your agent immediately figures out that it needs to run get_order first. Then, it checks the stock using list_products, looks up packaging options with list_packs, finds a spot in the warehouse via list_warehouse_slots, adjusts the count with update_stock, and finally uses all that info to verify the shipment status through list_shipments.
It's an automated, end-to-end logistics system you run right from your chat window. You don't leave the conversation; you just get stuff done.
019dd15b-35e8-7309-bb25-48419b85a333 
Here's how it actually works
The bottom line is your AI client acts as a dedicated logistics coordinator, running specific checks on demand so you don't have to switch tabs.
Subscribe to the ShippingBo server and provide your API credentials via Vinkius.
Your AI client sends a natural language request (e.g., 'Check stock for SKU 456').
The agent uses the appropriate tool (like get_product or list_orders) and returns the data directly into the chat.
Who is this actually for?
This tool is for operational staff who run e-commerce fulfillment daily. If you spend time clicking between inventory dashboards, order management systems, and carrier tracking portals—you need this. It's for the people whose job involves keeping the flow of goods moving, minimizing manual data lookups, and preventing stock discrepancies.
Uses update_stock to manually adjust counts after physical audits. Uses list_warehouse_slots to confirm if an item can actually fit on a shelf.
Runs list_orders and then uses get_order repeatedly to pull full order details when coordinating with customer service or accounting.
Relies on list_shipments to quickly get the latest tracking status for a client, eliminating the need to log into the carrier's website.
What Changes When You Connect
Stop switching between dashboards. You can get a full picture of your fulfillment pipeline by running list_orders and then immediately calling get_order to pull specific details—all in one conversation. This saves time and context-switching fatigue.
Inventory updates become instantaneous. Instead of logging into the WMS, you just tell your agent, 'Increase stock for SKU 123 by 50,' and it executes the update_stock tool immediately.
Shipping visibility is centralized. Use list_shipments to check dozens of orders at once, getting status updates (In Transit, Delivered) without ever touching a carrier's website or portal.
Never guess where something is stored again. Calling list_warehouse_slots gives you the real-time physical map, confirming if an item can actually be picked and packed before dispatching it.
Product data retrieval is precise. Need to know the dimensions for customs? Use get_product to pull all metadata on a specific SKU immediately, which is much faster than cross-referencing multiple database tables.
See it in action
Handling High-Volume Stock Adjustments
A warehouse manager realizes 50 units of Product X were damaged during receiving. Instead of logging into the WMS and navigating menus, they simply prompt their agent: 'Run update_stock for Product X, reducing count by 50.' The stock level is instantly corrected for fulfillment.
Fulfilling a Complex Order
A customer needs to know the status of three different shipments. They prompt their agent, which uses list_shipments. The agent then confirms: 'Shipment A is delivered; Shipment B is in transit and tracking progress is available via this link.' The problem is solved without logging into three separate carrier sites.
Catalog Auditing
An e-commerce analyst needs to check if a new product was entered correctly. They first run list_products to confirm the SKU exists, and then use get_product to validate all dimensions and pricing metadata against their requirements.
Pre-Packing Verification
Before dispatching a large order, an ops worker checks if enough space is reserved. They run list_warehouse_slots to confirm available capacity, ensuring the physical storage supports the incoming volume before calling for new inventory.
The honest tradeoffs
Checking stock manually
Going to the WMS portal, searching by SKU, clicking through several pages of filters until they find the current count.
Just tell your agent: 'What is the current stock level for Product ID 456?' The agent uses get_product or update_stock and gives you the number instantly.
Misunderstanding order scope
Trying to find a specific order detail when the system requires an order ID, but only knowing the customer's name.
First, use list_orders to narrow down the list of potential orders. Then, feed that resulting Order ID into the get_order tool for the full details.
Ignoring physical space
Processing an order and thinking it will fit in the warehouse without checking if a slot is actually open.
Before finalizing dispatch, always call list_warehouse_slots to confirm that the required storage area is physically available for new inventory.
When It Fits, When It Doesn't
Use this server if your workflow involves constant handoffs between different operational systems: Order Management (O), Warehouse Management System (WMS), and Carrier Tracking. You need a single point of truth to verify data across these domains.
Don't use this just because you want better reporting; those are separate analytics tools. This server is for action. If your only task is generating reports from raw order data, use a dedicated BI platform. But if the job requires 'Check stock levels AND update them AND find out where they are stored,' then ShippingBo nails it.
The key boundary: If you need to know what's available in the physical world (slot capacity), run list_warehouse_slots. If you just need to check how many units of a SKU exist, use get_product. Never assume the count from one tool is final without confirming it with another.
Questions you might have
How do I list all products in my ShippingBo catalog using the MCP Server? +
You call list_products. This tool pulls a comprehensive listing of every active SKU, giving you the full inventory scope right from your chat interface.
What is the difference between list_orders and get_order in ShippingBo? +
list_orders gives you an overview—a bulk list of all orders. You use get_order when you need deep, specific metadata for a single order ID.
Can I check warehouse slot availability with the ShippingBo MCP Server? +
Yes, call list_warehouse_slots. This tool lets you monitor and confirm physical storage capacity, ensuring you know exactly where items are stored before they get picked.
Does updating stock using update_stock affect current orders? +
The agent handles the transaction flow. After running update_stock, your AI client can immediately check if any pending orders can now be fulfilled, confirming the change's impact.
How do I track multiple shipments in ShippingBo? +
Use the list_shipments tool. It retrieves status and tracking data for a group of outgoing packages, allowing you to monitor dozens of deliveries at once.
How do I configure API access credentials for using `get_product`? +
You need an active API Token and User ID from your ShippingBo dashboard. Your agent uses these keys to authorize the connection, so make sure they're up-to-date before you try running any tool.
Does `update_stock` automatically handle negative inventory checks? +
Yes, the system validates that product stock counts cannot drop below zero when you run this update. If a negative count is detected for a specific SKU, the tool fails and returns an error code.
How do I retrieve large volumes of data using `list_orders`? +
The server handles pagination automatically for bulk requests. If you need more than the default batch size, just tell your agent to 'get the next page' and it will continue retrieving records until all orders are listed.
Can my AI automatically update the stock count for a specific product just by providing its ID? +
Yes! Use the update_stock tool. Provide the Product ID and the new stock count, and your agent will synchronize it across your ShippingBo warehouses instantly.
How do I monitor the status of warehouse slots to see how my inventory is organized? +
Simply ask the agent to run the list_warehouse_slots action. It will retrieve the full list of storage slots configured in your ShippingBo account.
How do I find my ShippingBo API credentials? +
Log in to your ShippingBo account, navigate to Settings > API, and you will find your unique API User (X-API-USER) and Token (X-API-TOKEN) there.
We've already built the connector for ShippingBo. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.