Everything in Remote is accessible through the interface that best suits how you build.
The Remote 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.
Link 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, employ the CLI for operational tasks, and connect MCP to let AI 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 runs on sandbox data.
Request access, sign in, and start testing.
$ remote sandbox --init
Access a sandbox preloaded with employees, contracts, payroll, and expenses. Use realistic data to test connectors, including API calls, CLI workflows, and integrations, without touching production.
You sign in and that's all. Authentication, permissions, and the compliance posture flow through unchanged.
Sign in through your browser or use an API token, the same way you log into Remote. Remote does not ask you to generate API keys or store secrets, and your credentials never touch the tool you use.
Your permissions in Remote apply across the CLI, API, and MCP. An employee sees employee data, an admin sees employer data, and nothing more.
The CLI, API, and MCP provide specific, structured endpoints rather than raw database access. Remote controls the responses, so you receive clean data without bulk exports or unstructured dumps.
Remote returns only the data you request, and only to the tool or agent you've authenticated. Your workforce data won't be used to train any AI provider's models.
The CLI, API, and MCP operate under Remote's established security and compliance posture, with the same rigour you already trust.
Whether you embed Remote, build integrations, or add AI features, Remote supplies the appropriate interface for each workflow. The API supports durable integrations. The CLI accelerates your teams' build and operational tasks. MCP exposes Remote 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 faster, speeding up implementation and support.
Continue to build on Remote's public API for the durable integrations you've 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. No API keys to rotate. No secrets to store. Your permissions in Remote carry across every surface.
For individual users logging in via the browser (CLI, MCP).
For customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.