Everything in Remote is accessible via the interface that best suits how you build.
The Remote API is engineered for production. Create reliable integrations that sync workforce data, automate business processes, and power applications over the long term.
The Remote CLI speeds up everyday tasks. 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 construct 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 need AI to interact with your workforce data. Most teams use a combination of all three.
Employees, contracts, payroll, and expenses — sample data that lets you test API calls, CLI commands, and integrations without risking real records.
Try connector workflows, debug integrations, and validate commands. Every test runs on sandbox data.
Request access, sign in, and 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, and that's all. Authentication, permissions, and the compliance posture all carry through.
Sign in via your browser or use an API token, the same method you use to access Remote. We don't require you to create API keys or keep secrets, and your credentials never touch the tool you use.
Your Remote permissions apply equally to the CLI, API, and MCP. An employee can view employee data, an admin can view employer data, and no additional access is granted.
The CLI, API, and MCP expose defined, structured endpoints rather than direct database access. Remote governs returned data, so you receive clean results without bulk exports or unstructured dumps.
Remote transmits only the data you request, and only to the tool or agent you signed in with. Your workforce data is not used to train any AI provider's models.
The CLI, API, and MCP operate under Remote's existing security and compliance posture, with the same rigour you already trust.
If you're embedding Remote, developing integrations, or adding AI capabilities, Remote offers the appropriate interface for each workflow. The API enables durable integrations. The CLI helps teams build and operate more quickly. MCP exposes Remote to AI agents.
As with Personio, BambooHR, and others, you deliver global employment for your customers via Remote. The CLI lets your team test workflows in sandbox, diagnose issues, and run operational tasks faster, accelerating implementation and support.
Continue to build on Remote's public API for the durable integrations you've developed. The CLI enables your team to test endpoints, validate workflows, and troubleshoot issues more quickly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, building an integration, or attaching an AI tool, authentication stays simple and secure. No API keys to rotate. No secrets to store. Your Remote permissions carry through to each surface.
For individual users signing in via the browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.