Everything in Remote is accessible through the interface that works best for how you build.
The Remote API is built for production. Create reliable integrations that sync workforce data, automate business processes, and power applications over the long term.
The Remote CLI makes everyday tasks faster. Manage your workforce, automate recurring jobs, and access Remote without leaving the command line.
Connect ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and build AI assistants that understand your organisation.
The API, CLI and MCP are designed to work together.
Build production integrations with the API, use the CLI for operational tasks, and connect MCP when you want AI to interact with your workforce data. Most teams combine all three.
Employees, contracts, payroll, expenses — sample data that lets you test API calls, CLI commands, and integrations without risking actual records.
Try connector workflows, debug integrations, validate commands. Every test is on sandbox data.
Request access, sign in, start testing.
$ remote sandbox --init
Access a sandbox preloaded with employees, contracts, payroll, and expenses. Test your connectors, including API calls, CLI workflows, and integrations, on realistic data without touching production.
You sign in. That is all. Authentication, permissions and the compliance posture all carry over.
Sign in through your browser or use an API token, the same way you log into Remote. We don't ask you to generate API keys or store secrets, and your credentials never touch the tool you're using.
Whatever permissions you have in Remote, you have through the CLI/API/MCP. An employee sees employee data, an admin sees employer data, and nothing more.
The CLI/API/MCP expose specific, structured endpoints, not raw database access. Remote controls what's returned, so you get clean data without bulk exports or unstructured dumps.
Remote sends only what you ask for, and only to the tool or agent you've signed into. Your workforce data isn't used to train any AI provider's models.
The CLI, API, and MCP run on Remote's existing security and compliance posture, with the same rigor you already trust.
Whether you are embedding Remote, building integrations or adding AI capabilities, Remote supplies the appropriate interface for every workflow. The API powers durable integrations. The CLI helps your teams build and operate faster. MCP exposes Remote to AI agents.
Like Personio, BambooHR, and others, you provide global employment for your customers through Remote. The CLI helps your team test workflows in sandbox, debug issues, and run operational tasks faster—speeding up implementation and support.
Continue building on Remote's public API for the durable integrations you've created. The CLI helps your team test endpoints, validate workflows, and debug issues faster.
All three surfaces (API, CLI, MCP) offer flexible auth. If you are writing a script, building an integration or connecting an AI tool, authentication remains simple and secure. No API keys to rotate. No secrets to store. Your permissions in Remote apply across every surface.
For individual users logging in via browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, complete the quickstart and begin working in real time.