Remote Retrieval MCP server
9 operations0 webhooks
Create equipment-return orders, track pending, new and in-progress shipments, and read company details and live device prices with Remote Retrieval.
Try Remote Retrieval with your agent
Connect Remote Retrieval, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Remote Retrieval on my account, then run one read-only example and show me the result.
Remote Retrieval tools and triggers
Tools are what your agent can do in Remote Retrieval through Corsair's MCP server. Triggers are the Remote Retrieval events a routine can start from.
Orders
- CreateWrite
Create one or more equipment-return orders. Each order is a real, paid shipment: Remote Retrieval mails a box to the named employee's home address and bills the account the per-device fee shown by prices
orders.create
- GetRead-only
Read one order by ID, taking it as the oid query parameter
orders.get
- InprogressRead-only
List orders whose return has started but whose device has not arrived yet, with both shipment legs
orders.inprogress
- ListRead-only
List every order with its payment status and shipping status, paged by the response's own next link
orders.list
- NewRead-only
List orders whose payment completed and which are ready to process
orders.new
- PendingRead-only
List orders whose payment has not completed; they are on hold until it does
orders.pending
Company
- GetRead-only
Read the company record the key belongs to: name, address and creation date
company.get
Prices
- PricesRead-only
Read the live per-device prices, including the Monitor_27 band for 24-to-27-inch displays
prices
Validate
- ValidateRead-only
Check that the API key works and read the account email it belongs to
validate
Connect Remote Retrieval to Claude, ChatGPT or Cursor
- 1
Connect Remote Retrieval in Corsair
Add your Remote Retrieval API key once in Corsair. Corsair stores the credential encrypted and makes the Remote Retrieval API calls for your agent, so it never goes into a prompt or a config file. Connect Remote Retrieval
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Remote Retrieval. On a ChatGPT personal plan, connect Remote Retrieval here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of Remote Retrieval's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 1 write, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/remoteretrieval, add the Remote Retrieval plugin, and connect with an API key. Then call methods like corsair.remoteretrieval.api.company.get() from your app. Corsair keeps each tenant isolated.
Yes. Remote Retrieval requires an API key from your Remote Retrieval account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Remote Retrieval, GitHub, Notion, Stripe, and the rest. Trigger Remote Retrieval from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for create equipment-return orders, track pending, new and in-progress shipments, and read company details and live device prices with Remote Retrieval. Common builds include sync jobs, admin tooling, and agents that call Remote Retrieval APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Remote Retrieval API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/remoteretrieval in the open repo. When Remote Retrieval ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Remote Retrieval data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Remote Retrieval data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Remote Retrieval on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the Remote Retrieval operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.