Everything in Remote is accessible via the interface that suits the way you build.
The Remote API is built for production. Create dependable 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.
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 let 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, and that is all. The authentication, permissions and compliance posture are carried over.
Sign in through your browser or use an API token, as you would when logging into Remote. We don't ask you to create API keys or retain secrets, and your credentials never touch the tool you use.
Your permissions in Remote apply equally to the CLI, API and MCP. An employee can access employee data, an admin can access employer data, and nothing beyond that.
The CLI, API and MCP expose defined, structured endpoints rather than direct database access. Remote determines what is returned, so you receive tidy data without bulk exports or unstructured dumps.
Remote transmits only the data you request, and only to the tool or agent you've signed into. Your workforce data is not used to train any AI provider's models.
The CLI, API and MCP inherit Remote's existing security and compliance posture, with the same rigour you already trust.
Whether you embed Remote, create integrations or add AI capabilities, Remote supplies the appropriate interface for each workflow. The API supports long‑lived 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 helps your team test workflows in a sandbox, debug issues and run operational tasks more quickly—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're 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 persist across every surface.
For individual users signing in through a browser (CLI, MCP).
For direct customer scripts and back-end automation.
For partner integrations.
Sign in, follow the quickstart and start working in real time.