Everything in Remote is accessible via the interface that suits how you build.
The Remote API is designed for production. Build 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 built to operate together.
Build production integrations via the API, use the CLI for operational tasks and connect MCP when AI needs to interact with your workforce data. Most teams use all three together.
Employees, contracts, payroll and expenses — sample data that lets you test API calls, CLI commands and integrations without risking real records.
Try connector workflows, troubleshoot 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, and that’s it. Authentication, permissions and the compliance posture all carry over.
Sign in via your browser or use an API token — the same method you use to access Remote. We don’t require you to create API keys or store secrets, and your credentials never touch the tool in use.
Your permissions in Remote apply equally to the CLI, API and MCP. Employees can view employee data; admins can see employer data — and nothing beyond that.
The CLI, API and MCP expose defined, structured endpoints rather than raw database access. Remote governs responses so you receive tidy 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. Your workforce data will not be used 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 trust.
If you're embedding Remote, creating integrations or adding AI features, Remote supplies the appropriate interface for each workflow. The API supports long‑lived integrations. The CLI helps your teams build and run things faster. MCP enables AI agents to access Remote.
Like Personio, BambooHR and others, you can deliver global employment for your customers through Remote. The CLI lets your team test workflows in a sandbox, troubleshoot issues and run operational tasks more quickly—accelerating implementation and support.
Keep developing on Remote’s public API for the durable integrations you've built. The CLI helps your team test endpoints, validate workflows and debug problems more quickly.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, building an integration or connecting an AI tool, signing in is straightforward and secure. No API keys to rotate. No secrets to store. Your Remote permissions apply across every surface.
For individual users signing in through 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.