EasyPost MCP integration for AI agents.
Connect AI agents to EasyPost through 6 structured actions, including get address, create address, and create tracker. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 6
- 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 EasyPost integration exposes
The EasyPost Agent App exposes 6 provider-backed actions for productivity and location work. Its current contract lets an authorized agent retrieve an easypost address by id, create an immutable easypost address for shipping workflows, and create an easypost standalone tracker from a carrier tracking code. 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 EasyPost account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real EasyPost capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_addressREADRetrieve an EasyPost address by ID.
INPUTS: address_id
create_addressWRITECreate an immutable EasyPost address for shipping workflows.
INPUTS: street1 / street2 / city / state / zip
create_trackerWRITECreate an EasyPost standalone tracker from a carrier tracking code.
INPUTS: tracking_code / carrier
get_trackerREADRetrieve an EasyPost tracker by ID.
INPUTS: tracker_id
list_carrier_typesREADList carrier types available to the EasyPost account.
list_trackersREADList EasyPost trackers with pagination and optional carrier filters.
INPUTS: before_id / after_id / page_size / start_datetime / end_datetime
INPUT CONTRACTS
Know what the action needs before it runs.
get_address
address_idOPTIONAL- The EasyPost resource ID.
create_address
street1REQUIRED- The first line of the address.
street2OPTIONAL- The second line of the address.
cityREQUIRED- The full city name.
stateREQUIRED- The state or province.
zipREQUIRED- The ZIP or postal code.
create_tracker
tracking_codeREQUIRED- The tracking code associated with the package.
carrierOPTIONAL- The carrier associated with the tracking code.
get_tracker
tracker_idOPTIONAL- The EasyPost resource ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Address
Retrieve an EasyPost address by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_addressControl Create Address
Create an immutable EasyPost address for shipping workflows. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_addressVerify with Get Tracker
Retrieve an EasyPost tracker by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_trackerSAFETY BOUNDARY
Operate EasyPost with explicit limits
- Authorize EasyPost with API key and grant only the provider access required by the selected actions.
- 2 actions are 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 EasyPost rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the EasyPost task completed successfully.
CONNECTION MODEL
API key
EasyPost API key used as the Basic authentication username. Create or manage keys in EasyPost account settings: https://app.easypost.com/account/settings?tab=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
- 4
- WRITE SIGNALS
- 2
- 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 EasyPost.