Logistics
ShipEngine MCP connector
The ShipEngine connector brings carriers, batches, labels and account settings into Claude, ChatGPT and Cursor, so your team can build a batch, process its labels or check a carrier balance by asking, inside their own ShipEngine access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect ShipEngine to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ShipEngine once
-
Open Connections, choose Add connection, and pick ShipEngine.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a ShipEngine API key. One person generates a token in ShipEngine and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect ShipEngine to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect ShipEngine to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect ShipEngine to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect ShipEngine to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with ShipEngine through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Fulfillment
Build the morning batch from a list
Create a ShipEngine batch, add the day's shipments to it and remove the ones that are on hold, all from one request. Then process the labels when the pick list is confirmed.
-
Warehouse
Find out why a batch failed
Ask which shipments in a ShipEngine batch came back with errors and what the carrier said about each one, then fix the addresses and send the batch again.
-
Operations
Check which carriers and services are live
List every carrier connected to the ShipEngine account, the services and package types each one offers, and the options available before choosing how to ship a new product line.
-
Finance
Top up a carrier account balance
See which carriers are running low on postage funds in ShipEngine and add funds to the right one before the afternoon pickup, with the action recorded against your name.
-
Ecommerce
Connect a new carrier account
Add a new carrier connection to ShipEngine when you sign a regional courier, and remove a carrier account you no longer use so it stops appearing in rate choices.
-
Brand
Keep label logos current
Upload a new logo image to ShipEngine settings, swap it in for the old one and check which images are still in use, without opening the dashboard.
Try asking
- “Which batches failed processing this week”
- “Show me open shipments by carrier”
- “List settings images added this month”
AI tools
ShipEngine tools for your AI agents
96 tools are ready to call through Elaichi's MCP endpoint the moment you connect ShipEngine, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting ShipEngine gets you
6 screens from the product, each doing one job for your ShipEngine account.
The agent
Ask shipping questions, get real answers.
Ask about shipments, rates and batches in plain language and get answers from live records.
- batches
- settings images
- shipments
- account settings
Ask Elaichi to work across your apps.
Which batches failed processing this week
Show me open shipments by carrier
List settings images added this month
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared keys.
Connect Claude, ChatGPT or Cursor to one governed ShipEngine endpoint with no SDK required.
Copy the endpoint
Tool catalog
96 ShipEngine tools, zero custom code.
Browse every ShipEngine method, resource and batch operation ready to call without writing code.
- List all ShipEngine account settings
- List all ShipEngine settings images
- Create a ShipEngine settings image
- Get single ShipEngine settings image by ID
Toolboxes
Every team gets its own toolbox.
Give sales, support and fulfilment separate ShipEngine toolboxes scoped to their own work.
- Fulfilment
- Support
- Finance
- Operations
Shared connections
Delegated access, no shared credentials ever.
See who connected each ShipEngine account and how many teams and members use it.
- Fulfilment US
- Fulfilment EU
- Support
- Finance
Audit log
Every shipment action, logged and answerable.
See who did what in ShipEngine, when it happened, and which resource it touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules trigger shipping work, people approve it.
A schedule fetches ShipEngine batches, drafts a digest, and posts back once a person approves.
ShipEngine digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch batches
ShipEngine
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
ShipEngine
Queued
Collections and dashboards
ShipEngine health, computed on a schedule.
Track batches created over 14 days by team with no model involved in the numbers.
ShipEngine health
Refreshed 4 minutes ago · every 15 minutes · from the batches collection
Batches
1,284 ↓ 12%
Settings images
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Batches created
Last 14 days
By team
Share of activity
Fulfilment US 34%
Fulfilment EU 27%
Support 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect ShipEngine to Claude?
Connect ShipEngine in Elaichi first: open the ShipEngine connector, paste an API key from your ShipEngine dashboard, and save. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and ShipEngine appears as a connector in Claude.
Does ShipEngine work with ChatGPT and Cursor as well as Claude?
Yes. Once ShipEngine is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect ShipEngine once and every client you use picks it up.
What can an AI agent actually do with my ShipEngine data?
It can list the carriers connected to your ShipEngine account with their services, package types and options, add funds to a carrier, and connect or remove a carrier account. It can create and update batches, add or remove shipments from them, show which shipments in a batch have errors, and process the labels. It can also read your ShipEngine account settings and manage the logo images used on labels. Because ShipEngine has a large number of actions, short concrete asks such as "show errors in today's batch" work better than long paragraphs.
Does connecting ShipEngine give the AI access to every carrier account?
Only what the ShipEngine API key you connected can already reach, and never more. Each person signs in to Elaichi as themselves, so their calls to ShipEngine are logged under their name, and an administrator can narrow what they may do, for example read carriers but never add funds. Elaichi can restrict ShipEngine access; it can never widen it beyond the key.
Can I stop an agent from deleting or changing things in ShipEngine?
Yes. Restrictions in Elaichi apply per action, so you can allow listing ShipEngine carriers and batches while blocking deleting a batch, removing a carrier or adding funds. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a ShipEngine connection when someone leaves?
Offboarding that person in Elaichi ends their access to ShipEngine at once, across every client they used. If they shared a ShipEngine connection with a team, it keeps working for everyone else. When you want ShipEngine gone entirely, disconnect it once in Elaichi and it is removed from Claude, ChatGPT, Cursor and every other client at the same time.
Put ShipEngine in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.