Pipe17 MCP Server
Connects Claude and other Model Context Protocol clients to Pipe17, so you can ask about your orders, shipments, fulfillments, products, inventory, integrations and more in plain language, and make a few changes to orders.
Setup
The server URL is:
https://mcp.pipe17.com/mcp
You sign in with your Pipe17 account. One login reaches every Pipe17 org your account belongs to, and you pick the org in the conversation.
Claude (claude.ai and Claude Desktop)
Add a custom connector with the URL above. When Claude asks you to connect, sign in with your Pipe17 account.
Claude Code
claude mcp add --transport http pipe17 https://mcp.pipe17.com/mcp
Then run /mcp in Claude Code and sign in.
Other MCP clients
Any client that supports the Streamable HTTP transport and OAuth can connect to the URL above.
API keys
A Pipe17 API key works on the per-org URL instead, sent in the x-pipe17-key header:
https://mcp.pipe17.com/mcp/{orgKey}
Replace {orgKey} with the key of the org the API key belongs to. In Pipe17, it's shown at the top of Settings > Profile. The plain /mcp URL accepts sign-ins only.
Tools
43 tools. 4 of them change data: Cancel Order, Create Sales Order, Fulfill Order, Update Order. Every other tool only reads.
| Tool | Access | What it does |
|---|---|---|
Cancel Ordercancel-order |
Writes | Cancels a whole order: sets its status to canceled and cancels and restocks every open shipment on it. Cancelling individual line items is not supported. Asks you to confirm first |
Create Sales Ordercreate-sales-order |
Writes | Creates a new sales order in the system. Automatically initiates fulfillment workflow. Requires external order ID and line items with SKUs, quantities, and prices. |
Fulfill Orderfulfill-order |
Writes | Creates a fulfillment record for an order, indicating items have been shipped. Requires order ID, tracking number, and line items. |
Update Orderupdate-order |
Writes | Updates an existing order with new information. It can't cancel an order: use cancel-order, which asks the user to confirm first. |
Get Automationget-automation |
Reads | Get a specific automation by ID. |
Get Customerget-customer |
Reads | Get a specific customer by ID. |
Get Exceptionget-exception |
Reads | Get a specific exception by ID. |
Get Fulfillmentget-fulfillment |
Reads | Get a specific fulfillment by ID. |
Get Fulfillments by Orderget-fulfillments-by-order |
Reads | Retrieve all fulfillments for an order by external order ID |
Get Integrationget-integration |
Reads | Get a specific integration by ID. |
Get Locationget-location |
Reads | Get a specific location by ID. |
Get Orderget-order |
Reads | Get a specific order by ID. |
Get Order by External IDget-order-by-external-id |
Reads | Retrieve order details by external order ID from other systems (e.g., "ORDER-123", "WOO-456", "SHOP-789") |
Get Order Routingget-order-routing |
Reads | Get a specific order routing by ID. |
Get Productget-product |
Reads | Get a specific product by ID. |
Get Schema Mapping Contextget-schema-mapping-context |
Reads | Get the requisite context for explaining a mapping rule including vendor schema, default mapping, and public mapping |
Get Schema Mappingsget-schema-mappings |
Reads | Retrieve schema mappings for an integration |
Get Shipments by Orderget-shipments-by-order |
Reads | Retrieve all shipments for an order by external order ID |
Get Shipping Requestget-shipping-request |
Reads | Get a specific shipping request by ID. |
List Automation Ruleslist-automation-rules |
Reads | List automation rules. |
List Automation Runslist-automation-runs |
Reads | List automation runs. |
List Automationslist-automations |
Reads | List automations. |
List Customerslist-customers |
Reads | List customers. |
List Eventslist-events |
Reads | List events. |
List Exceptionslist-exceptions |
Reads | List exceptions. |
List Fulfillmentslist-fulfillments |
Reads | List fulfillments. |
List Integrationslist-integrations |
Reads | List integrations. |
List Inventorylist-inventory |
Reads | List inventory. |
List Jobslist-jobs |
Reads | List jobs. |
List Locationslist-locations |
Reads | List locations. |
List Noteslist-notes |
Reads | List notes. |
List Order Routing Runslist-order-routing-runs |
Reads | List order routing runs. |
List Order Routingslist-order-routings |
Reads | List order routings. |
List Orderslist-orders |
Reads | List orders. |
List Organizationslist-organizations |
Reads | List the Pipe17 orgs this login can reach, with each org's orgKey, name, accountId and isHoldingOrg. Only on /mcp |
List Productslist-products |
Reads | List products. |
List Shipping Requestslist-shipping-requests |
Reads | List shipping requests. |
Search Customersget-customers |
Reads | Retrieves customer information including contact details, addresses, and order history. |
Search Fulfillmentsget-fulfillments |
Reads | Retrieves fulfillment records including shipping details, tracking numbers, and delivery status. |
Search Inventoryget-inventory |
Reads | Retrieves inventory levels across warehouses and locations. |
Search Ordersget-orders |
Reads | Retrieves orders details when you need to check order status, view line items, track fulfillment progress, or investigate customer inquiries. |
Search Product Variantsget-product-variants |
Reads | Retrieves product variant information (child products with different sizes, colors, or other attributes). |
Search Productsget-products |
Reads | Retrieves product catalog information including SKUs, names, descriptions, and inventory details. |
Permissions
- Signed in, the connector acts as your Pipe17 user. It can reach only the orgs you belong to, and only what you can see there. With an API key, it reaches what that key can reach.
- An admin can turn AI access off for an org. Calls to that org are then refused.
- Tools that change data are marked as writes, so clients that ask before a write will ask. Cancel Order also asks you to confirm: the first call changes nothing and shows a summary of what will happen, and Claude is told to make the change only after you say yes. The server enforces the summary step; it can't tell your yes from the AI's, so your client's own approval prompt still matters.
- Results can include your customers' names and addresses, as they appear in Pipe17.
Troubleshooting
Asked to sign in again
Your login expired or was revoked. Reconnect the connector and sign in again.
"Pipe17 didn't accept this login"
Pipe17 refused this account. Reconnect and sign in again. If it keeps happening, ask your Pipe17 admin to check your user.
"needs an orgKey", or the wrong org
Your account reaches more than one org, so name the one you mean, or ask Claude to list your orgs. Tools that change data always need the org named.
"isn't one of the orgs this login can reach"
The account you signed in with isn't a member of that org. Ask Claude to list your orgs, or sign in with another account.
"AI access is turned off", or HTTP 403 "AI access disabled for this organization"
An admin of that org has to turn AI access on.
"different orgs in the last minute"
One login can query a limited number of orgs a minute. Narrow the question to fewer orgs, or wait a minute.
A confirmation expired
Confirmations last 5 minutes. When one expires, Claude gets a new summary; check it and confirm that one.
HTTP 503 "Authorization keys temporarily unavailable"
Pipe17's sign-in service was briefly unreachable, so the server couldn't check your login. Try again in a minute.
Still stuck?
Contact support@pipe17.com or visit the Pipe17 Help Center.