Use this guide when your AI assistant shows a Shipi error, reports a label that doesn’t exist, or doesn’t show the Shipi tools at all. If you haven’t connected yet, start with the Shipi MCP setup guide.
In this guide: Quick checklist · Error messages · Placeholder links · Tools not loading · Claude.ai asks for the key · Wrong store · Stopped working · Contact support · FAQ
Quick checklist
- The server URL is exactly
https://mcp.myshipi.com/api/mcp, including/api/mcp. - Your integration key is sent with every request: as the
Authorization: Bearer YOUR_INTEGRATION_KEYheader, or (Claude.ai) told to Claude in the chat. - The key is the current key of the right store (Settings → Websites & MCP). Keys stop working after Regenerate.
- Your Shipi account is active, has label balance, and has at least one carrier account switched on.
Fastest check: open Shipments in the Shipi dashboard. If the shipment isn’t there, no label was created, whatever the AI said.
Error messages and how to fix them
| Message | What it means | How to fix it |
|---|---|---|
Error: integration key required. Pass integration_key, send it as a Bearer token, or set SHIPI_INTEGRATION_KEY. | The request reached Shipi without an integration key. | Add the Authorization: Bearer YOUR_INTEGRATION_KEY header to your MCP connection, or (Claude.ai) tell Claude your key. See the setup guide. |
Invalid integration key or inactive account. | The key doesn’t match any active Shipi store. It was mistyped, regenerated, or the account is inactive. | Copy the key again from Settings → Websites & MCP and update your AI tool. |
Invalid integration key format. | The key is cut off or has extra characters. | Paste the key without quotes or spaces. The header must be Bearer, one space, then the key. |
Your Account is Deactivated due to the pending payment… | When creating a label: the key wasn’t recognised, or the account is deactivated because of an unpaid invoice. | Check the key first. If it’s correct, open Billing in Shipi or contact support. |
You dont have a label balance. Please upgrade to continue. | No labels left in your plan. | Upgrade or top up in Billing, then ask the AI to try again. |
Rate limit exceeded. Please upgrade your plan to continue using live shipping rates. | Your plan’s live-rates quota is used up. | Upgrade your plan in Billing. |
No carrier account found. Add one in Shipi > Carriers. | The store has no carrier account, or none is switched on. | Connect a carrier. See how to configure shipping accounts. |
Carrier account 123 not found. Use list_carriers to see your accounts. | The AI used an account ID that doesn’t exist in this store. | Ask the AI to list your carrier accounts and use one of those. |
carrier account 123 has no complete ship-from address saved. Pass shipper. | The carrier account has no full ship-from address. | Complete the shipper address in the carrier account settings, or give the AI the ship-from address. |
Error: recipient address is required. / Error: products are required… | Required shipment details are missing. | Give the AI the full recipient address, and each package’s weight and dimensions. |
Order creation failed. Mandatory data missing / Invalid carrier type. | The shipment request was incomplete. | Ask the AI to try again with the carrier account and service. Contact support if it keeps happening. |
Carrier messages, e.g. Fedex Error: … | The carrier rejected the shipment (credentials, address, service or package details). | Fix it in the carrier account settings or shipment details. See the FedEx, DHL Express and UPS setup guides. |
Invalid JSON response / Request failed: … | Shipi could not be reached or returned an unexpected answer. | Wait a minute and try again. If it continues, contact support with the time of the error. |
The AI says the label was created, but shows placeholder links
Symptoms: the answer contains text such as [Tracking Number Link], [Label Link] or (After processing), and the shipment is not in Shipi.
Cause: the AI never received a real result from Shipi. Usually the integration key was missing, so Shipi returned an error, and the AI filled the gap with a made-up success message. It can also happen when an app shows the model’s text without running its tool calls.
Fix:
- Make sure the integration key is sent (see the checklist above).
- Ask the AI: “Show me the exact response from the Shipi tool.” This reveals the real error message.
- Check Shipi → Shipments to confirm whether a label exists.
- If you built the app yourself: display tool errors to the user and instruct the model never to report a label, tracking number or link that isn’t in the tool result.
Shipi tools don’t show up in my AI tool
- Check the URL: it must be exactly
https://mcp.myshipi.com/api/mcp. - Restart the AI tool completely. Claude Desktop must be quit from the system tray or menu bar, not just closed.
- Claude Desktop with mcp-remote or the npm package needs Node.js 18 or later. Check the MCP logs under Settings → Developer.
- Claude.ai: open the tools menu in the chat and make sure the Shipi connector is switched on.
- Cursor: open Settings → MCP; the Shipi server should show as connected.
- VS Code: use Copilot Chat in Agent mode and run
MCP: List Serversfrom the command palette. - Tools that only support local (stdio) MCP servers can use mcp-remote as a bridge. See Claude Desktop Option A in the setup guide.
Claude.ai keeps asking for the integration key
Claude.ai connectors can’t store custom headers, and a new chat doesn’t remember the key from an earlier chat. Create a Claude Project for shipping and add this to the Project instructions:
My Shipi integration key is YOUR_INTEGRATION_KEY. Use it for every Shipi tool.The AI shows the wrong store’s carriers or shipments
Each Shipi store has its own integration key, and the AI always works with the store whose key it uses. Copy the key of the correct store from Settings → Websites & MCP. To work with several stores, add one MCP connection per store.
It worked before and suddenly stopped
- The key was regenerated in Shipi. Update it in every AI tool.
- Connections set up before 22 July 2026 that didn’t send a key must now send it with every request. Add the header (or tell Claude the key) as shown in the setup guide.
- The account ran out of label balance or live-rates quota.
- The account is deactivated because of a pending payment.
Still stuck? Contact support
Email support@myshipi.com or open a ticket at app.myshipi.com/support with:
- The AI tool you use (for example Claude.ai, Claude Desktop, Cursor or your own app)
- The date and time of the failed request
- What you asked the AI
- The exact error text
- Your store name (don’t post your integration key in public channels)
Frequently asked questions
Your AI tool reached the Shipi MCP server without sending your Shipi integration key. Send it as the header Authorization: Bearer YOUR_INTEGRATION_KEY, or in Claude.ai tell Claude your key in the chat.
The AI didn’t get a real result from Shipi, usually because the integration key was missing or the tool returned an error, and it filled the gap with placeholder text. Check that the key is sent and ask the AI to show the exact tool response.
Open Shipments in the Shipi dashboard. Every label created through MCP appears there with its tracking number and label file.
The most common causes are a regenerated integration key, a connection that never sent the key (required on every request since July 2026), no remaining label balance, or a deactivated account.
Email support@myshipi.com or open a ticket in the Shipi dashboard under Support. Include the AI tool, time of the request and the exact error text.
Related guides
- How to connect Shipi to Claude, Cursor and other AI tools (MCP setup)
- How to configure shipping accounts in Shipi
- Shipi API overview
Last updated: September 24, 2026