Everything in Remote is accessible via the interface that best suits your way of building.
The Remote API is engineered for production. Build reliable integrations that sync workforce data, automate business processes and power applications for 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 to query live workforce data, automate workflows and build AI assistants that understand your organisation.
The API, CLI and MCP are built to operate together.
Build production integrations with the API, use the CLI for operational tasks and connect MCP when AI needs 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 against Sandbox data.
Request access, sign in and begin testing.
$ remote sandbox --init
Access a Sandbox preloaded with employees, contracts, payroll and expenses. Test connectors — API calls, CLI workflows and integrations — on realistic data without impacting production.
You sign in once; that's all. Authentication, permissions and our compliance posture transfer automatically.
Sign in via your browser or use an API token, the same method you use for Remote. We never require generation of API keys or secret storage, and your credentials never reside within the tool.
Your Remote permissions carry over to the CLI, API and MCP. An employee will only see employee-level data; an admin sees employer data — and no additional access.
The CLI, API and MCP present defined, structured endpoints rather than direct database access. Remote governs responses so you receive orderly data without bulk exports or unstructured dumps.
Remote transmits only the data you request, and only to the specific tool or agent you've authenticated. We do not use your workforce data to train any AI provider's models.
The CLI, API and MCP operate under Remote's existing security and compliance framework, with the same rigour you rely on.
If you're embedding Remote, creating integrations or adding AI capabilities, Remote supplies the appropriate interface for each workflow. The API enables durable integrations, the CLI accelerates team development and operations, and MCP exposes Remote to AI agents.
As with Personio, BambooHR and other partners, you can deliver global employment to customers via Remote. The CLI lets your team test sandbox workflows, debug issues and perform operational tasks more quickly—accelerating implementation and support.
Maintain development on Remote's public API for the durable integrations you've already built. Use the CLI to test endpoints, validate workflows and debug issues more rapidly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether writing a script, building an integration or linking an AI tool, authentication remains straightforward and secure. There are no API keys to rotate and no secrets to store. Your Remote permissions apply across every surface.
For individual users signing in through 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.