# Redo MCP

> Redo manages returns, exchanges, and shipping protection claims through your AI agent. It connects your e-commerce operations to a single protocol layer, letting you track requests, calculate rates, approve claims, and process refunds without touching a dashboard. Stop switching tabs; manage the full post-purchase lifecycle in natural conversation.

## Overview
- **Category:** ecommerce
- **Price:** Free
- **Tags:** returns-management, shipping-protection, customer-experience, claims-processing, e-commerce-operations, logistics

## Description

You connect your **Redo** account to any AI agent using Model Context Protocol (MCP). This server gives your agent direct access to manage returns, exchanges, and shipping protection claims. You handle the entire post-purchase lifecycle—from initial request listing straight through refund processing—all in natural conversation without touching a dashboard. Stop switching tabs; you'll run the whole operation from one place.

**Reviewing Claim Status**
You can pull up a customer's full claim history immediately by calling `list_store_returns` or grabbing all specific metadata for one request with `get_return_details`. You'll also get basic info about the seller using `get_store_details`, and you'll see exactly what products are covered under policy when you use `list_protected_items`. To check how systems receive notifications, call `list_return_webhooks` to view active webhooks. For a quick rundown of current shipping rules, run `get_protection_summary`. You can also get real-time cost estimates for returning packages by calling `get_return_shipping_rates`.

**Updating the Return Lifecycle**
The server lets you change a return's status directly through your agent conversation. If the customer is good to go, you call `approve_return_claim`; if they aren't, you reject it using `reject_return_claim`, providing a reason right away. You can log private comments or team notes on any record by calling `add_internal_note`.

**Finalizing Financial Resolution**
When the job is done, you finalize the action—like issuing refunds, creating store credit, or setting up an exchange for damaged goods—by running `process_final_resolution`. You'll want to run `verify_api_connection` first just to make sure your agent client can talk to the Redo API endpoint correctly.

Your AI agent uses these tools to manage returns. It doesn't just view data; it executes the operational workflow.

## Tools

### add_internal_note
Adds a private comment or log entry to a specific return request record.

### approve_return_claim
Updates a claim's status, formally approving the customer's return request.

### verify_api_connection
Runs a test to confirm that the MCP server is properly connected to the Redo API endpoint.

### get_store_details
Retrieves basic metadata about the specific store or seller associated with the return.

### get_protection_summary
Retrieves high-level details about current shipping protection coverage rules and settings.

### get_return_details
Pulls all specific metadata for a single return request, including item IDs and purchase dates.

### get_return_shipping_rates
Calculates real-time shipping costs and options available for returning packages.

### list_protected_items
Lists all products that are currently covered under the shipping protection policy.

### list_store_returns
Retrieves a summary view of multiple returns and claims across the store.

### list_return_webhooks
Shows a list of active webhooks, confirming which internal systems receive return notifications.

### process_final_resolution
Finalizes a return or claim by executing definitive actions, like issuing refunds or creating exchanges.

### reject_return_claim
Updates a claim's status, formally rejecting the customer's return request and providing a reason.

## Prompt Examples

**Prompt:** 
```
List the last 5 pending return requests.
```

**Response:** 
```
Retrieving requests... I found 5 pending returns, including one from 'john@email.com' for 'Reason: Damaged in transit'. Would you like the full details?
```

**Prompt:** 
```
Approve the return claim for ID 'ret_abc123'.
```

**Response:** 
```
Claim approved! I have successfully updated the status of return ret_abc123 to 'approved'. The customer will receive their instructions automatically.
```

**Prompt:** 
```
Get the shipping rates for return 'ret_abc123'.
```

**Response:** 
```
Calculating rates... I found 3 shipping options for this return. Standard Ground is $8.50 and Express is $15.75. Which one would you like to select?
```

## Capabilities

### Review Claim Status
List all pending returns and protection claims, checking their current status and associated customer metadata.

### Update Return Lifecycle
Programmatically update a return's status (e.g., approved or rejected) directly from your agent conversation.

### Finalize Financial Resolution
Trigger final actions like refunds, store credit creation, or exchange orders for damaged/lost packages.

### Determine Coverage Scope
Access detailed information about shipping protection settings and which products are eligible for claims.

### Calculate Shipping Costs
Retrieve real-time shipping rates required to estimate return costs for customers or internal accounting.

### Log Internal Notes
Add private comments or communication logs to any specific return or claim record for team visibility.

## Use Cases

### The Damaged Item Claim
A customer contacts support: 'My jacket arrived ripped.' Your agent first calls `get_return_details` to verify the purchase ID. Next, it uses `get_protection_summary` to confirm coverage. Finally, since it's damaged, the agent runs `process_final_resolution` to automatically generate a replacement order.

### The Failed Return Attempt
A return request is submitted but lacks necessary documentation. Your agent calls `get_return_details`, sees the missing information, and uses `reject_return_claim` with a specific reason code. This prevents the customer from waiting for an invalid approval.

### Checking Complex Shipping Needs
A manager needs to advise on return costs for different geographies. The agent calls `get_return_shipping_rates`, pulling multiple carrier options and cost breakdowns so the manager can quote the best option immediately in chat.

### Auditing Past Claims
A quality assurance team needs to review all claims from a specific product line last month. They use `list_store_returns` to pull the batch data, then filter by status and add `add_internal_note` for follow-up.

## Benefits

- Stop manual dashboard hopping. Instead of checking 5 different tabs to find a return's status, use `list_store_returns` directly in your conversation flow.
- Speed up approvals. Your agent runs `get_return_details`, lets you review the metadata, and executes `approve_return_claim`—all without copy-pasting IDs or clicking buttons.
- Accurate cost estimates on demand. Need to quote a return shipment? Call `get_return_shipping_rates` to get current costs instantly, making your customer advice accurate every time.
- Automate the resolution step. Don't just track claims; use `process_final_resolution` to trigger refunds or credits immediately after approval, closing the loop completely.
- Full visibility into policy. Use `get_protection_summary` and `list_protected_items` to answer 'Is this covered?' questions accurately and quickly, preventing payment disputes.

## How It Works

The bottom line is you manage complex logistics workflows using simple chat prompts instead of navigating a suite of dashboards.

1. Subscribe to the Redo server via Vinkius Marketplace and provide your Store ID and API Secret.
2. Configure your AI client (Claude, Cursor, etc.) to recognize the MCP endpoints for Redo.
3. Instruct your agent: 'List all returns from John Doe.' The agent runs `list_store_returns` and presents actionable data.

## Frequently Asked Questions

**How do I list all pending returns using Redo MCP Server?**
Use the `list_store_returns` tool. This function retrieves a summary view of multiple claims and returns, letting you see which ones need attention at a glance.

**What is the difference between `approve_return_claim` and `process_final_resolution`?**
`approve_return_claim` only changes the status to 'Approved.' It’s the sign-off. You must then use `process_final_resolution` to actually trigger the money transfer or credit.

**Can I calculate shipping costs for a return? Which tool do I use?**
Yes, you use `get_return_shipping_rates`. This function pulls real-time rates and multiple carrier options based on the return's origin.

**How do I check if an item is covered for a claim?**
Call `get_protection_summary` to get high-level details about your coverage rules. For specific items, use `list_protected_items` to see the product list.

**I need to add a note to a claim; which tool is correct?**
Use `add_internal_note`. This posts a private comment or log entry directly onto the specific return record, keeping the communication history tied to that single claim.

**How do I verify that my Redo API credentials are correct using the `verify_api_connection` tool?**
It runs a simple check to confirm your connection status. This tool confirms if your Store ID and Secret key work with minimal calls, so you can catch authentication errors before running critical functions.

**What does the `list_return_webhooks` tool help me monitor about my return system?**
This tool lists all active webhook configurations. You use it to confirm your internal systems are correctly set up to receive real-time notifications for returns or claims, ensuring no data gets missed.

**If I need general background info on the store, which tool should I use: `get_store_details`?**
Use `get_store_details` to fetch high-level metadata about your Redo account. This gives you general business context without needing a specific return ID or claim number.

**How do I get my API Secret for Redo?**
Log in to your Redo dashboard, navigate to Settings > API, and you can generate or copy your active secret key.

**Are shipping protection claims handled differently than returns?**
No, Redo treats shipping protection claims (for lost, damaged, or stolen items) as a specific type of return record, accessible via the same tools.

**Can I approve a return request directly through the agent?**
Yes! Use the 'approve_return_claim' tool and provide the Return ID. The agent will update the status in Redo instantly.

**How do I see the reasons why customers are returning items?**
The 'get_return_details' tool retrieves the full metadata for any request, which includes the specific return reason code and customer comments.