Everything in Remote is accessible through the interface that best matches how you build.
Remote's API is built for production. Build 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 build AI assistants that understand your organisation.
The API, CLI, and MCP are designed to work together.
Create 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, expenses — sample data that lets you test API calls, CLI commands, and integrations without risking actual records.
Try connector workflows, debug integrations, and validate commands. Every test is 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. That is all. Authentication, permissions, and the compliance posture carry over.
Sign in via your browser or use an API token, the same method you use to log into Remote. You don't need to generate API keys or store secrets, and your credentials never touch the tool you use.
The permissions you hold in Remote extend to the CLI, API, and MCP. An employee can access employee data, an admin can access employer data, and nothing else.
The CLI, API, and MCP expose specific, structured endpoints rather than raw database access. Remote controls what is returned, so you receive clean data without bulk exports or unstructured dumps.
Remote delivers only the data you request, and only to the tool or agent you signed into. 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 expect.
If you embed Remote, build integrations, or add AI capabilities, Remote provides the right interface for each workflow. The API supports durable integrations, the CLI helps your teams develop and operate more quickly, and MCP exposes Remote to AI agents.
Like Personio, BambooHR, and others, you deliver global employment for your customers through Remote. The CLI helps your team test workflows in a Sandbox, debug issues, and run operational tasks more quickly, accelerating implementation and support.
Continue developing on Remote's public API for the durable integrations you have created. The CLI helps your team test endpoints, validate workflows, and debug issues more quickly.
All three surfaces — API, CLI, and MCP — support flexible authentication. Whether you are writing a script, building an integration, or connecting an AI tool, authentication is straightforward and secure. No API keys to rotate. No secrets to store. Your permissions in Remote carry through to every surface.
For individual users signing in via a browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.