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 create AI assistants that understand your organisation.
The API, CLI, and MCP are designed to work together.
Build production integrations via 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 real 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. Test connectors, including API calls, CLI workflows, and integrations, on realistic data without touching production.
You sign in and that's it. Authentication, permissions, and compliance posture carry through with your session.
Sign in via your browser or use an API token, just as you do for Remote. You won't need to create API keys or store secrets, and your credentials never touch the tool you connect.
Your permissions in Remote apply across the CLI, API, and MCP. An employee can view employee data, an admin can view employer data, and no additional access is granted.
The CLI, API, and MCP present specific, structured endpoints rather than raw database access. Remote controls the responses, so you receive clean data instead of bulk exports or unstructured dumps.
Remote only sends the data you request, and only to the tool or agent you authorised. Your workforce data is not 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.
If you're embedding Remote, building integrations, or adding AI capabilities, Remote supplies the appropriate interface for each workflow. The API supports durable integrations; the CLI lets your teams implement and operate more quickly. MCP makes Remote accessible to AI agents.
As with Personio, BambooHR, and others, you deliver global employment for your customers via Remote. The CLI lets your team test workflows in a sandbox, debug issues, and run operational tasks more quickly, speeding 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 resolve issues more quickly.
Each surface (API, CLI, MCP) supports flexible auth. Whether you're scripting, building an integration, or connecting an AI tool, authentication is 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 via browser (CLI, MCP).
For direct customer scripts and backend automation.
For partner integrations.
Sign in, follow the quickstart, and begin working in real time.