AfterShip Post-Purchase

Search AfterShip shipments and returns in Claude, then fix records or approve and resolve returns.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the AfterShip Post-Purchase connector does

The AfterShip Post-Purchase MCP server connects your AfterShip Tracking and Returns data to Claude. Its 22 tools search shipments and returns, and 12 of them change records: correcting shipment details, retracking parcels, marking a final status, and approving, receiving or resolving returns. AfterShip says every write waits for your explicit approval.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

AfterShip Post-Purchase tools (22)

  • add_return_allowlist
  • add_return_blocklist
  • add_return_comment
  • approve_return
  • get_field_options
  • get_return
  • get_return_workflow
  • get_shipment
  • list_return_allowlist
  • list_return_blocklist
  • list_return_workflow
  • list_returns
  • list_shipments
  • list_tracking_filter_options
  • mark_shipment_status
  • receive_return_items
  • reject_return
  • remove_return_allowlist
  • remove_return_blocklist
  • resolve_return
  • retrack_shipment
  • update_shipment

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Some writes are permanent. AfterShip lists what no connector tool can do: un-approve, un-reject or un-receive a return, reopen a resolved return, delete a return comment, or reverse a manually marked shipment status.
  • Receiving is not idempotent. A repeated receive_return_items call adds another batch. If unsure whether a call succeeded, re-read the return rather than retrying.
  • Refunds only. Resolving supports refund outcomes; exchanges are not supported yet.
  • Plan-gated. Tracking and Returns tools each need their own AfterShip plan.
  • One organisation, your role. Access is limited to the organisation chosen at sign-in and to your role's permissions.
  • Exact-match lookups. Partial tracking numbers or email fragments return nothing.
  • Customer personal data. Shipment tools read and can edit customer names, emails and phone numbers, and those values pass through the AI provider you connect.
  • What we could check. We saw the 401 challenge and the scope descriptor. AfterShip's developer page for this server, aftership.com/docs/post-purchase-mcp, returned HTTP 403 to our client, so this page relies on AfterShip's help-centre article and the directory.

Frequently asked questions

Why does the AfterShip connector return a subscription link instead of data?

Because your organisation does not have the plan that tool needs. AfterShip's help article states that tracking tools require an AfterShip Tracking plan and returns tools require an AfterShip Returns plan. Without the matching plan, the tool returns a link to subscribe rather than any shipment or return data. Check which products your organisation pays for before assuming the connector is broken.

Why is the AfterShip connector showing the wrong organisation's data?

Because the connector is tied to the organisation you picked when you signed in. AfterShip's help article says the fix is to remove the connector, add it again, and choose the correct organisation at the sign-in step. The connector can only see that one organisation at a time, and only what your own AfterShip role is allowed to see inside it.

Why does the assistant keep asking for the full tracking number or email?

Because AfterShip lookups are exact matches. The help article states that partial tracking numbers or fragments of an email address will not resolve, so the assistant asks for the complete value instead of guessing. Give the whole tracking number, order number or customer email, and the shipment or return lookup will work as expected in the conversation.

Why will the assistant not reject a return or record an inspection grade?

Because AfterShip requires those values to come from you. Its help article states that the assistant must not invent values: a rejection reason and an inspection grade must be supplied by the user, and name, email and phone changes must be confirmed verbatim. Tell the assistant the reason or the grade, then approve the change it shows you before it runs.

Sources

Use it in an agent

Put AfterShip Post-Purchase to work.

Connect AfterShip Post-Purchase once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.