Does AfterShip have an MCP server?
AfterShip maintains an official MCP server.
- Access
- Remote server
- Endpoint
- https://mcp.aftership.com/post-purchase
- Category
- E-Commerce
A remote server run by AfterShip itself — nothing to install. Documented at support.aftership.com.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http aftership https://mcp.aftership.com/post-purchaseAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.aftership.com/post-purchase - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"aftership": {
"url": "https://mcp.aftership.com/post-purchase"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"aftership": {
"type": "http",
"url": "https://mcp.aftership.com/post-purchase"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.aftership.com/post-purchase - Complete sign-in, then enable the connector in a new chat
Does AfterShip have an official MCP server?
Yes. AfterShip maintains an official MCP server, hosted at https://mcp.aftership.com/post-purchase.
How do I connect AfterShip to Claude?
Add https://mcp.aftership.com/post-purchase as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http aftership https://mcp.aftership.com/post-purchase" in Claude Code.
Do I need to install anything to use the AfterShip MCP server?
No. It is a remote server hosted by AfterShip, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
AfterShip's help center documents its OAuth Post-purchase MCP server at mcp.aftership.com/post-purchase (answers MCP initialize with 401); a separate no-auth public tracking server mcp.aftership.com/tracking/public is published to the MCP Registry under AfterShip's namespace com.aftership.mcp and in the AfterShip/tracking-and-returns-mcp repo, but returned 429 (shared rate limit exhausted) when checked. GitHub metadata is refreshed every six hours.
AfterShip's help center documents its OAuth Post-purchase MCP server at mcp.aftership.com/post-purchase (answers MCP initialize with 401); a separate no-auth public tracking server mcp.aftership.com/tracking/public is published to the MCP Registry under AfterShip's namespace com.aftership.mcp and in the AfterShip/tracking-and-returns-mcp repo, but returned 429 (shared rate limit exhausted) when checked.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.