Shipday MCP integration for AI agents.
Connect AI agents to Shipday through 7 structured actions, including get order, create order, and delete order. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Shipday integration exposes
The Shipday Agent App exposes 7 provider-backed actions for productivity and location work. Its current contract lets an authorized agent retrieve one shipday delivery order by order number, insert a shipday delivery order, and delete a shipday delivery order by order id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Shipday account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Shipday capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_orderREADRetrieve one Shipday delivery order by order number.
INPUTS: orderNumber
create_orderWRITEInsert a Shipday delivery order.
INPUTS: orderNumber / customerName / customerAddress / customerPhoneNumber / restaurantName
delete_orderHIGH IMPACTDelete a Shipday delivery order by order ID.
INPUTS: orderId
edit_orderWRITEEdit an existing Shipday delivery order.
INPUTS: orderId / orderNo / customerName / customerAddress / customerEmail
get_order_progressREADRetrieve real-time delivery progress and ETA for a Shipday order.
INPUTS: trackingId / isStaticDataRequired
list_active_ordersREADRetrieve active delivery orders from Shipday.
list_carriersREADRetrieve carriers configured in Shipday.
INPUT CONTRACTS
Know what the action needs before it runs.
get_order
orderNumberREQUIRED- The Shipday order number.
create_order
orderNumberREQUIRED- The alphanumeric identifier for the order.
customerNameREQUIRED- The name of the customer.
customerAddressREQUIRED- The address of the customer.
customerPhoneNumberREQUIRED- The phone number of the customer with country code.
restaurantNameREQUIRED- The name of the restaurant.
delete_order
orderIdREQUIRED- The positive Shipday identifier.
edit_order
orderIdREQUIRED- The positive Shipday identifier.
orderNoREQUIRED- The numeric or alphanumeric identifier for the order.
customerNameREQUIRED- The name of the customer.
customerAddressREQUIRED- The address of the customer.
customerEmailREQUIRED- The email address of the customer.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Order
Retrieve one Shipday delivery order by order number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_orderControl Create Order
Insert a Shipday delivery order. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_orderVerify with Get Order Progress
Retrieve real-time delivery progress and ETA for a Shipday order. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_order_progressSAFETY BOUNDARY
Operate Shipday with explicit limits
- Authorize Shipday with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_order` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Shipday rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Shipday task completed successfully.
CONNECTION MODEL
API key
Shipday API key used as the Authorization: Basic header value. Create or view it from the Shipday dashboard API settings: https://docs.shipday.com/reference.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Shipday.