17TRACK MCP integration for AI agents.
Connect AI agents to 17TRACK through 4 structured actions, including get quota, register trackings, and get tracking details. Review authentication, inputs…
- ACTION CONTRACTS
- 4
- 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 17TRACK integration exposes
The 17TRACK Agent App exposes 4 provider-backed actions for productivity and location work. Its current contract lets an authorized agent get the current tracking and email quota counters for the 17track account, register up to 40 tracking numbers for automatic tracking by 17track, and get current tracking details for up to 40 registered tracking numbers. 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 17TRACK account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real 17TRACK capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_quotaREADGet the current tracking and email quota counters for the 17TRACK account.
register_trackingsWRITERegister up to 40 tracking numbers for automatic tracking by 17TRACK.
INPUTS: trackings
get_tracking_detailsREADGet current tracking details for up to 40 registered tracking numbers.
INPUTS: trackings
list_trackingsREADList registered 17TRACK shipments with status, time, and pagination filters.
INPUTS: tracking_numbers / carrier / data_origin / package_status / register_time_from
INPUT CONTRACTS
Know what the action needs before it runs.
register_trackings
trackingsOPTIONAL- Tracking numbers to register.
get_tracking_details
trackingsOPTIONAL- Tracking numbers to retrieve.
list_trackings
tracking_numbersOPTIONAL- Tracking numbers to filter by.
carrierOPTIONAL- The numeric 17TRACK carrier code.
data_originOPTIONAL- The source used to register the tracking number.
package_statusOPTIONAL- The current main package status.
register_time_fromOPTIONAL- The start of the registration time range.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Quota
Get the current tracking and email quota counters for the 17TRACK account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_quotaControl Register Trackings
Register up to 40 tracking numbers for automatic tracking by 17TRACK. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
register_trackingsVerify with Get Tracking Details
Get current tracking details for up to 40 registered tracking numbers. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_tracking_detailsSAFETY BOUNDARY
Operate 17TRACK with explicit limits
- Authorize 17TRACK with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in 17TRACK rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the 17TRACK task completed successfully.
CONNECTION MODEL
API key
17TRACK API key sent in the 17token header. Get or change the key in 17TRACK API Settings: https://api.17track.net/admin/settings.
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
- 1
- HIGH IMPACT
- 0
- 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 17TRACK.