Adspirer Retail Media Ads
Plan and optimise Amazon Ads and Walmart Connect campaigns from Claude.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
receive_return_items call adds another batch. If unsure whether a call succeeded, re-read the return rather than retrying.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.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.
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.
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.
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.
https://mcp.aftership.com/post-purchase (2026-11-18): anonymous initialize returned HTTP 401 with a WWW-Authenticate header naming the descriptor and 16 scopes; /.well-known/oauth-protected-resource/post-purchase returned 200 with the same 16 scopes and https://accounts.aftership.com/auth/realms/business as the authorization server. No tool was called. · retrieved 2026-11-18documentation value. Returned HTTP 403 to our client on 2026-11-18; not cited for any claim. · retrieved 2026-11-18docs/marketing/data/anthropic-directory-2026-11-17.json. Source for the partner tier, the 2026-07-06 listing date, the endpoint, transport and the 22 tool names. · retrieved 2026-11-17Connect AfterShip Post-Purchase once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.