# ShipHero MCP connector

The ShipHero connector brings warehouse bills, ad hoc charges, carrier and custom boxes, assembly components and client accounts to Claude, ChatGPT, Cursor and Microsoft Copilot, so each person works with ShipHero inside their own access.

Source: https://elaichi.ai/connectors/shiphero/

## Facts

| | |
| --- | --- |
| Application | ShipHero |
| Category | Ecommerce |
| AI tools | 202 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ShipHero is connected

- List every unsubmitted ShipHero bill for this month
- Add a $45 rush pick charge to the Acme account
- Which custom boxes have not been updated since last year?

## Connect ShipHero in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ShipHero.
2. Optionally set Share with, then press Connect.
3. Paste a ShipHero API key. One person generates a token in ShipHero and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ShipHero tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ShipHero MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## ShipHero MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## ShipHero MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## ShipHero MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## ShipHero MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect ShipHero to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a ShipHero tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ShipHero through Elaichi

### Review a client's bill before it goes out

Finance. Pull up a ShipHero bill, check the line items against the month's charges, recalculate it and submit it once the numbers look right.

### Add a one-off charge without opening ShipHero

Billing. Record an ad hoc charge for extra pallet handling or a rush pick straight from the chat, then correct the amount if the client questions it.

### Keep box sizes current

Warehouse. List the carrier boxes and custom boxes in use, update dimensions when a supplier changes packaging, and remove a custom box nobody packs with anymore.

### Update a kit when a component changes

Kitting. Swap, update or clear the assembly components for a bundle in bulk when a supplier substitutes a part, instead of editing each kit by hand.

### Answer a client's billing question in seconds

Client services. Find the client's ShipHero account, list their recent bills and charges, and reply with the exact figures while they are still on the phone.

### Clear the unsubmitted bill backlog every Monday

Operations. Ask for every ShipHero bill still waiting on a recalculation or a submission and work through the list before invoicing day.

## Elaichi vs Zapier MCP vs Composio for ShipHero

All three can connect ShipHero to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ShipHero tools | Allow or restrict single ShipHero tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ShipHero call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect ShipHero to Claude?

Connect ShipHero in Elaichi by pasting a ShipHero API key, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once it is added, Claude can work with ShipHero bills, charges and boxes inside your own sign-in.

### Does ShipHero work with ChatGPT and Cursor as well as Claude?

Yes. The same endpoint, https://api.elaichi.ai/mcp, serves Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. Connect ShipHero once in Elaichi and every client picks it up.

### What can an AI agent actually do with my ShipHero data?

It can pull up a ShipHero bill, list open bills for a client account, add or update an ad hoc charge, recalculate and submit a bill, and look up carrier boxes and custom boxes. It can also add, update or clear assembly components when a kit changes. Short, specific asks such as listing this month's unsubmitted bills for one client work better than long paragraphs.

### Does connecting ShipHero give the AI access to every account and bill?

No. Every request runs inside the access of the person who signed in, so the agent sees only the ShipHero accounts, bills and charges that person can already see. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one ShipHero connection?

Yes. One person connects ShipHero with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every bill or charge change in ShipHero.

### Can I stop an agent from deleting or changing things in ShipHero?

Yes. Restrictions in Elaichi apply per action, such as deleting a ShipHero bill or custom box, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a ShipHero connection when someone leaves?

Offboarding that person in Elaichi ends their access to ShipHero at once, across every client. A shared ShipHero connection keeps working for everyone else on the team. If you ever want to remove ShipHero entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the ShipHero MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. ShipHero is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for ShipHero?

Yes. Both let Claude, ChatGPT or Cursor use ShipHero. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ShipHero call.

### How is Elaichi different from Composio for ShipHero?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ShipHero: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 202 ShipHero tools

Every tool below is callable through https://api.elaichi.ai/mcp once ShipHero is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a ShipHero access token** (Create). Get a ShipHero access token: POST /auth/refresh with the stored refresh token, or POST /auth/token with the username and password on first connect. The connector calls this on connect and once a day; you rarely need it directly. Required: refresh_token, or username and password (taken from the connected account, not from the caller).
- **List all ShipHero account** (List). Fetch account records matching the supplied arguments.
- **List all ShipHero ad hoc charges** (List). Fetch ad hoc charges matching the supplied arguments. Required: ids. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero ad hoc charge** (Create). Creates an ad hoc charge for a customer. When a bill is given, adds the charge to it. That bill must be a draft. Required: customer_account_id, name, description, occurred_at, labor_unit_id, unit_amount, rate. Send the AddBillAdHocChargeInput fields as the request body (ShipHero mutation bill_add_ad_hoc_charge).
- **Update a ShipHero ad hoc charge by ID** (Update). Updates an ad hoc charge. Fails if the charge is on a bill that is not a draft. Required: id. The id is the adhoc_charge_id. Send the UpdateBillAdHocChargeInput fields as the request body (ShipHero mutation bill_update_ad_hoc_charge).
- **Create a ShipHero assembly component** (Create). Adds one or more components to a product assembly. Required: assembly_sku, components. Send the AddAssemblyComponentsInput fields as the request body (ShipHero mutation assembly_add_components).
- **ShipHero assembly components bulk clear** (Clear). Removes every component from a product assembly. Required: assembly_sku. Send the ClearAssemblyComponentsInput fields as the request body (ShipHero mutation assembly_clear_components).
- **ShipHero assembly components bulk delete** (Delete). Removes one or more components from a product assembly. Required: assembly_sku, components. Send the RemoveAssemblyComponentsInput fields as the request body (ShipHero mutation assembly_remove_components).
- **ShipHero assembly components bulk update** (Update). Changes the quantity of one or more components in a product assembly. Required: assembly_sku, components. Send the UpdateAssemblyComponentsInput fields as the request body (ShipHero mutation assembly_update_components).
- **Create a ShipHero bill recalculation** (Create). Recalculates a bill's charges as a new bill. Fails if the bill is finalized, deleted, or already recalculating. Required: id. Send the RecalculateBillInput fields as the request body (ShipHero mutation bill_recalculate).
- **Get single ShipHero bill by ID** (Get). Fetch bill records matching the supplied arguments. Required: id.
- **List all ShipHero bills** (List). Fetch bills matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero bill** (Create). Creates a bill for a customer covering a date range and starts calculating its charges. The customer must have a billing profile. Required: customer_account_id, start_date, end_date. Send the CreateBillInput fields as the request body (ShipHero mutation bill_create).
- **Delete a ShipHero bill by ID** (Delete). Deletes a bill. Required: id. The id is the id. Send the DeleteBillInput fields as the request body (ShipHero mutation bill_delete).
- **ShipHero bills submit** (Action). Sends a finalized bill to the customer by email. The customer must have bill access, and each bill can be submitted only once. Required: id. Send the SubmitBillInput fields as the request body (ShipHero mutation bill_submit).
- **Update a ShipHero bill by ID** (Update). Changes a bill's status to draft, finalized, or paid. Paid bills cannot be updated. Required: id, status. The id is the id. Send the UpdateBillInput fields as the request body (ShipHero mutation bill_update).
- **Get single ShipHero carrier box by ID** (Get). Fetch carrier box records matching the supplied arguments. Required: id. The id is the box_code.
- **List all ShipHero carrier boxes** (List). Fetch carrier boxes matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Update a ShipHero carrier box by ID** (Update). Updates the price or quantity on hand of a carrier box in a warehouse. Required: id, warehouse_id. The id is the box_code. Send the UpdateCarrierBoxInput fields as the request body (ShipHero mutation carrier_box_update).
- **Get single ShipHero custom box by ID** (Get). Fetch custom box records matching the supplied arguments. Required: id.
- **List all ShipHero custom boxes** (List). Fetch custom boxes matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero custom box** (Create). Creates a custom box for a warehouse with its dimensions, price, and quantity on hand. Required: name, warehouse_id, dimensions. Send the CreateCustomBoxInput fields as the request body (ShipHero mutation custom_box_create).
- **Delete a ShipHero custom box by ID** (Delete). Deletes a custom box. Required: id. The id is the custom_box_id. Send the DeleteCustomBoxInput fields as the request body (ShipHero mutation custom_box_delete).
- **Update a ShipHero custom box by ID** (Update). Updates a custom box. Omitted fields keep their current values. Required: id. The id is the custom_box_id. Send the UpdateCustomBoxInput fields as the request body (ShipHero mutation custom_box_update).
- **Create a ShipHero cycle count recount** (Create). Creates a cycle count that recounts items flagged with discrepancies in an earlier count. Required: name, warehouse_id. Send the CreateRecountCycleCountInput fields as the request body (ShipHero mutation cycle_count_recount_create).
- **Get single ShipHero cycle count by ID** (Get). Fetch cycle count records matching the supplied arguments. Required: id.
- **List all ShipHero cycle counts** (List). Fetch cycle counts matching the supplied arguments. Required: warehouse_id. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **List all ShipHero data exports** (List). Fetch data export files for the authenticated account. Required: export_types.
- **Get single ShipHero fulfillment invoice by ID** (Get). Fetch fulfillment invoice records matching the supplied arguments. Required: id.
- **List all ShipHero fulfillment invoices** (List). Fetch fulfillment invoices matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero fulfillment status** (Create). Creates a custom order fulfillment status for your account or a 3PL customer account. Required: name. Send the CreateOrderFulfillmentStatusInput fields as the request body (ShipHero mutation order_fulfillment_status_create).
- **List all ShipHero inbound shipment images** (List). Fetch inbound shipment images matching the supplied arguments. Required: inbound_shipment_id.
- **Get single ShipHero inbound shipment location summary by ID** (Get). Fetch inbound shipment location summary records matching the supplied arguments. Required: id. The id is the inbound_shipment_id.
- **Get single ShipHero inbound shipment summary by ID** (Get). Fetch inbound shipment summary records matching the supplied arguments. Required: id. The id is the inbound_shipment_id.
- **Get single ShipHero inbound shipment by ID** (Get). Fetch inbound shipment records matching the supplied arguments. Required: id.
- **List all ShipHero inbound shipments** (List). Fetch inbound shipments matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero inbound shipment** (Create). Creates an inbound shipment for a warehouse, linked to purchase orders and a vendor, with carrier, dock, and truck schedule details. Required: warehouse_id. Send the CreateInboundShipmentInput fields as the request body (ShipHero mutation inbound_shipment_create).
- **Update a ShipHero inbound shipment by ID** (Update). Updates the warehouse, purchase orders, carrier, and truck details of an inbound shipment. Required: id, warehouse_id, purchase_orders_ids. The id is the inbound_shipment_id. Send the UpdateInboundShipmentInput fields as the request body (ShipHero mutation inbound_shipment_update).
- **Create a ShipHero inventory addition** (Create). Adds on-hand quantity of a SKU to a warehouse location or license plate (LPN). Required: sku, warehouse_id, quantity. Send the UpdateInventoryInput fields as the request body (ShipHero mutation inventory_add).
- **List all ShipHero inventory changes** (List). Fetch inventory changes matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Create a ShipHero inventory removal** (Create). Removes on-hand quantity of a SKU from a warehouse location or license plate (LPN). Required: sku, warehouse_id, quantity. Send the UpdateInventoryInput fields as the request body (ShipHero mutation inventory_remove).
- **Create a ShipHero inventory replacement** (Create). Sets the on-hand quantity of a SKU in a warehouse location to an exact value. Required: sku, warehouse_id, quantity. Send the ReplaceInventoryInput fields as the request body (ShipHero mutation inventory_replace).
- **Get single ShipHero inventory snapshot by ID** (Get). Fetch inventory snapshot records matching the supplied arguments. Required: id. The id is the snapshot_id.
- **List all ShipHero inventory snapshots** (List). Fetch inventory snapshots matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **ShipHero inventory snapshots cancel** (Cancel). Cancels an inventory snapshot that is still being generated. Required: snapshot_id. Send the InventoryAbortSnapshotInput fields as the request body (ShipHero mutation inventory_abort_snapshot).
- **Create a ShipHero inventory snapshot** (Create). Starts building a snapshot of inventory in the background. When it is ready, a notification is sent to the given email address or URL. Send the InventoryGenerateSnapshotInput fields as the request body (ShipHero mutation inventory_generate_snapshot).
- **Create a ShipHero inventory subtraction** (Create). Same as inventory_remove. Removes on-hand quantity of a SKU from a warehouse location or LPN. Required: sku, warehouse_id, quantity. Send the UpdateInventoryInput fields as the request body (ShipHero mutation inventory_subtract).
- **List all ShipHero inventory sync items** (List). Fetch inventory sync items status matching the supplied arguments. Required: sync_id. The connector pages through all results (50 per page; nested lists show their first 10 records).
- **Get single ShipHero inventory sync by ID** (Get). Fetch inventory sync status matching the supplied arguments. Required: id.
- **List all ShipHero inventory syncs** (List). Fetch inventory sync statuses matching the supplied arguments. The connector pages through all results (50 per page; nested lists show their first 10 records).
- ...and 152 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
