AfterShip MCP integration for AI agents.
Connect AI agents to AfterShip through 9 structured actions, including get tracking, create tracking, delete tracking, and detect couriers. Review authentica…
- ACTION CONTRACTS
- 9
- 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 AfterShip integration exposes
The AfterShip Agent App exposes 9 provider-backed actions for productivity and location work. Its current contract lets an authorized agent retrieve one aftership tracking record by tracking id, create an aftership tracking record for a shipment, and delete an aftership tracking record by tracking 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 AfterShip account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AfterShip capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_trackingREADRetrieve one AfterShip tracking record by tracking ID.
INPUTS: id / fields / lang
create_trackingWRITECreate an AfterShip tracking record for a shipment.
INPUTS: id / tracking_number / slug / slug_group / shipment_tags
delete_trackingHIGH IMPACTDelete an AfterShip tracking record by tracking ID.
INPUTS: id
detect_couriersREVIEWDetect possible AfterShip couriers for a tracking number.
INPUTS: tracking_number / slug / destination_postal_code / tracking_ship_date / tracking_account_number
list_couriersREADList AfterShip couriers, optionally limited to active couriers or slugs.
INPUTS: active / slug
list_trackingsREADList AfterShip trackings with cursor pagination and shipment filters.
INPUTS: cursor / limit / keyword / tracking_numbers / slug
mark_tracking_completedREVIEWMark an AfterShip tracking record as completed by ID.
INPUTS: id / reason / event_datetime
retrack_trackingREVIEWAsk AfterShip to retrack an expired tracking record by ID.
INPUTS: id
update_trackingWRITEUpdate editable fields on an AfterShip tracking record.
INPUTS: id / slug / title / order_id / custom_fields
INPUT CONTRACTS
Know what the action needs before it runs.
get_tracking
idREQUIRED- The AfterShip tracking ID.
fieldsOPTIONAL- A comma-separated list of response fields to include.
langOPTIONAL- The language code used to translate checkpoint messages.
create_tracking
idOPTIONAL- A custom tracking ID. AfterShip generates one if omitted.
tracking_numberREQUIRED- The carrier tracking number of the shipment.
slugOPTIONAL- The AfterShip courier slug, such as dhl, ups, or usps.
slug_groupOPTIONAL- A courier slug group such as fedex-group.
shipment_tagsOPTIONAL- Shipment tag strings attached to the tracking.
delete_tracking
idOPTIONAL- The AfterShip tracking ID.
detect_couriers
tracking_numberREQUIRED- The carrier tracking number to inspect.
slugOPTIONAL- Courier slugs to limit auto-detection to.
destination_postal_codeOPTIONAL- The destination postal code.
tracking_ship_dateOPTIONAL- The shipping date in YYYYMMDD format.
tracking_account_numberOPTIONAL- The shipper's carrier account number.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Tracking
Retrieve one AfterShip tracking record by tracking ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_trackingControl Create Tracking
Create an AfterShip tracking record for a shipment. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_trackingVerify with List Couriers
List AfterShip couriers, optionally limited to active couriers or slugs. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_couriersSAFETY BOUNDARY
Operate AfterShip with explicit limits
- Authorize AfterShip 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_tracking` 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 AfterShip rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AfterShip task completed successfully.
CONNECTION MODEL
API key
AfterShip API key used with the as-api-key header. Create or manage API keys in AfterShip organization settings: https://admin.aftership.com/settings/api-keys.
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
- 3
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 3
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 AfterShip.