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.
Connect ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and develop 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, 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, 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's it. Authentication, permissions, and the compliance posture all carry over.
Sign in via your browser or use an API token, the same way you access Remote. We don't ask you to create API keys or store secrets, and your credentials never touch the tool you use.
Your permissions in Remote apply to the CLI, API, and MCP. An employee can access employee data, an admin can access employer data, and no extra data is exposed.
The CLI, API, and MCP provide defined, structured endpoints rather than raw database access. Remote determines what is returned, so you receive orderly data instead of bulk exports or unstructured dumps.
Remote sends only what you request, 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 operate under Remote's existing security and compliance posture, with the same rigour you trust.
Whether you embed Remote, build integrations, or add AI capabilities, Remote supplies the appropriate interface for each workflow. The API supports durable integrations. The CLI helps your teams develop and operate more quickly. 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 the sandbox, debug issues, and run operational tasks more quickly, accelerating 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 resolve issues faster.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, building an integration, or linking an AI tool, authentication is straightforward 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 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.