# AfterShip Returns MCP MCP > AfterShip Returns automates your entire reverse logistics pipeline. Use this MCP to manage return requests, audit RMAs, approve returns, and process item receipts—all through natural conversation with your AI client. Stop manually checking statuses; get full visibility into every step of the customer's return journey. ## Overview - **Category:** ecommerce - **Price:** Free - **Tags:** returns-management, rma-processing, shipping-labels, reverse-logistics, customer-experience, automated-returns ## Description Handling product returns used to be a bureaucratic nightmare. You'd have to jump between multiple tabs just to check if a request was pending, confirm the item details against an RMA number, and then generate a label before finally marking it as received in your warehouse system. This MCP changes that process entirely. Your AI agent manages all of this orchestration—from initial customer inquiry to physical inventory update—using simple chat commands. It acts as a central nervous system for your returns flow. Connecting to the Vinkius catalog makes these advanced capabilities instantly available to any compatible client, letting you automate complex reverse logistics processes without writing a single line of code. ## Tools ### approve_return Authorizes an awaiting return request, immediately generating the necessary shipping label for the customer to send the item back. ### get_return_details Retrieves comprehensive information on a specific RMA, detailing items, original reasons for return, and current logistics status. ### list_returns Gathers lists of customer returns, showing both pending inquiries and past requests along with their processing statuses. ### receive_items Logs the arrival of physical goods at the facility, recording their condition and grading for inventory purposes. ## Prompt Examples **Prompt:** ``` List all pending return requests from the last 48 hours. ``` **Response:** ``` I've retrieved your pending return requests. You have 5 new inquiries from customers like Sarah J. and Michael B. Would you like to see the return reasons for these items? ``` **Prompt:** ``` Approve return request ID 'ret_abc123'. ``` **Response:** ``` I've successfully approved return request ret_abc123. The customer has been notified, and the RMA status is now 'Approved'. Would you like to check if a shipping label was generated? ``` **Prompt:** ``` Show me details for RMA number 'RMA-98765'. ``` **Response:** ``` I've retrieved the details for RMA-98765. It includes 2 items: 'Blue Cotton Shirt' (Wrong size) and 'Canvas Tote' (Defective). The return shipment is currently in transit via UPS. ``` ## Capabilities ### Audit all return requests List and check the status of customer returns both pending and historical. ### Gather detailed RMA information Retrieve technical metadata for a specific Return Merchandise Authorization, including item lists and stated reasons for return. ### Authorize and label returns Approve pending requests instantly, triggering the generation of required shipping labels. ### Manage physical inventory receipts Record that items have arrived at the warehouse and assign them a grading condition for restocking purposes. ## Use Cases ### A customer asks for a return on a defective item. The agent first uses `list_returns` to confirm the request exists. Next, they run `get_return_details` to verify the exact item and defect reason. If everything checks out, they execute `approve_return`, telling the customer immediately that their label is ready. This whole process takes seconds. ### The warehouse receives a batch of returned products. Instead of having staff manually enter data into a sheet, the ops manager simply tells the AI agent to run `receive_items`. The system logs the items and confirms their grade (e.g., 'Good' or 'Needs Repair'), updating inventory automatically. ### A customer complains about delayed tracking. Support uses the MCP to quickly check the return status using `list_returns` and then calls `get_return_details`. The agent can immediately tell the customer not only that the request is approved, but also what the specific item details are. ### A bulk of returns needs processing after a sale. The e-commerce team uses `list_returns` to pull all pending requests from the last week. They can then systematically use `get_return_details` on each one, identifying patterns or bottlenecks in the return policy before approving them. ## Benefits - Stop guessing on status. Use `list_returns` to pull up a full list of pending or historical requests and see exactly where each one is stuck in the pipeline. - Save time investigating returns. Instead of checking multiple databases, use `get_return_details` to instantly find item specifics and the original reason for return on any RMA number. - Close the loop on approvals. When a request is ready, call `approve_return`. This single action notifies the customer and automatically generates the required shipping label. - Streamline your warehouse process. Use `receive_items` to record when goods arrive at the facility, assigning them a grading condition right from the chat interface. - Improve visibility across departments. By automating the entire flow—from viewing status with `list_returns` to confirming receipt with `receive_items`—you give both support and warehouse staff clear data. ## How It Works The bottom line is you stop navigating multiple systems. You ask your AI client, and it handles the data flow across all required logistics endpoints. 1. Subscribe to this MCP and enter your AfterShip API Key. 2. Connect your AI client (Claude, Cursor, etc.) to Vinkius and activate the returns toolset. 3. Ask your agent a question like: 'What's the status for RMA-98765?' The system executes the necessary checks and provides a consolidated answer. ## Frequently Asked Questions **How do I check the status of all returns using list_returns?** Use `list_returns` when you need an overview. This tool pulls up both pending and historical requests, giving you a quick dashboard view of where every customer return stands. **Do I need to use get_return_details before approving returns?** Yes. Always call `get_return_details` first. This ensures you have the full context—item list and specific return reasons—before committing to an approval via `approve_return`. **What if I approve a return but items aren't received? Do I still need receive_items?** Yes. Even after approving the initial request, you must use `receive_items` when the goods physically arrive at your warehouse to log them and record their condition. **Can this MCP help me process returns for a specific RMA number?** Absolutely. You can check details using `get_return_details`, then if approved, trigger the label generation with `approve_return` all from one prompt. **What specific permissions are required to run `approve_return`?** The API key needs read and write scopes. This ensures your agent can not only verify the request status but also trigger the actual label generation process successfully. **If running `list_returns`, what filters can I apply to narrow down results?** You can filter by date range and specific statuses like 'Pending' or 'Overdue'. This prevents you from having to manually sift through months of historical return data. **If the `approve_return` tool fails, how do I troubleshoot the error?** Check the provided error message for invalid IDs or required steps. Often, running `get_return_details` first confirms if all necessary item information is present before attempting approval. **Does calling `receive_items` automatically update external customer records?** No, using `receive_items` updates the internal grade and arrival date. If you need to notify a customer or trigger an action outside of AfterShip's system, you must follow up with your own notification tool.