Integration

Retriever integration

Retriever ships boxes to remote employees so they can return company laptops, monitors and cell phones, and ships new devices out from its warehouse. Submit a device return order for an employee and follow its box and device tracking, create a deployment order that sends a stored device to an employee, list and inspect devices held in the Retriever warehouse, and read the organization's prepaid balances. Submitting a return or deployment order is billed (a return can be cancelled from the Retriever portal within 30 minutes). Authentication is a per-user API key from the Retriever portal, sent as a Bearer token in the Authorization header.

Connect Retriever How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Retriever.Built from the 9 Retriever tools below, on the connection you add once.

What you can do with Retriever

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Deployment, 3 operations

create_deploymentCreate deploymentPOSTCreates a BILLED deployment order: Retriever ships a device it holds for you to the employee, optionally with a return label. Returns the deployment id for get_deployment. HTTP 402 means no prepaid deployment is left.
get_deploymentGet deploymentGETGets one deployment order by id (from list_deployments or create_deployment): device, employee, shipping speed, return label settings and the shipment with its tracking.
list_deploymentsList deploymentsGETLists the organization's device deployment orders (devices sent out to employees), up to 50 per page; follow next with the cursor param. Each carries its id for get_deployment and its shipment.

Device return, 3 operations

create_device_returnCreate device returnPOSTSubmits a BILLED device return order: Retriever ships a box to the employee and the device back to company_info's address. Returns the order id for get_device_return. Cancellable in the Retriever portal within 30 minutes only.
get_device_returnGet device returnGETGets one device return order by id (from list_device_returns or create_device_return): device, employee and return addresses, shipments with box and device tracking, and the disposal certificate link when one exists.
list_device_returnsList device returnsGETLists the organization's device return orders, newest first, up to 50 per page; follow next with the cursor param. Each order carries its id (for get_device_return), device, status of its shipments and tracking.

Warehouse device, 2 operations

get_warehouse_deviceGet warehouse deviceGETGets one warehouse device by id (from list_warehouse_devices): serial number, manufacturer, model, specifications, condition and status.
list_warehouse_devicesList warehouse devicesGETLists the devices the organization stores in the Retriever warehouse, newest first, up to 50 per page; follow next with the cursor param. Each carries its id, serial number, model, condition and status.

Prepaid balance, 1 operation

list_prepaid_balancesList prepaid balancesGETLists the organization's prepaid balances: prepaid credits left per device type and the insurance credits. Check it before create_device_return or create_deployment, which answer HTTP 402 when the account cannot be billed.

Use Retriever from Claude Code, Cursor or Codex

Connect Retriever in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Retriever operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Retriever

Create your workspace
Sign up free. Nothing to install.
Connect Retriever once
Add your Retriever connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.