Everything in Remote is accessible via the interface that suits how you build best.
The Remote API is built for production. Build reliable integrations that synchronise 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.
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 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 actual 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 once. The authentication, permissions, and compliance posture then carry over.
Sign in via your browser or use an API token, just as you sign into Remote. We don't require you to generate API keys or store secrets, and your credentials never touch the tool you use.
Whatever permissions you hold in Remote apply equally through the CLI, API, and MCP. An employee can view employee data, an admin can view employer data, and nothing else.
The CLI, API, and MCP expose specific, structured endpoints rather than raw database access. Remote controls the 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 have 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 trust.
Whether you are embedding Remote, building integrations, or adding AI capabilities, Remote provides the appropriate interface for each workflow. The API supports durable integrations. The CLI helps your teams build and operate more quickly. MCP makes Remote accessible to AI agents.
Like Personio, BambooHR, and others, you deliver global employment for your customers through Remote. The CLI lets your team test workflows in sandbox, debug issues, and run operational tasks more quickly, speeding up implementation and support.
Continue building 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, MCP) support flexible authentication. Whether you are writing a script, building an integration, or connecting an AI tool, authentication remains simple and secure. There are no API keys to rotate, and no secrets to store. Your permissions in Remote apply across every surface.
For individual users signing in via a browser (CLI, MCP).
For direct customer scripts and back-end automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.