All of Remote is accessible via the interface that best suits your development approach.
The Remote API is designed for production use. Build dependable integrations that sync workforce data, automate business processes, and power applications over time.
The Remote CLI speeds up routine tasks. Manage your workforce, automate recurring jobs, and access Remote without opening the dashboard.
Link ChatGPT, Claude, Cursor, or any MCP-compatible client to Remote. Query live workforce data, automate workflows, and construct AI assistants that understand your organisation.
The API, CLI and MCP are built to operate together.
Develop production integrations via the API, employ the CLI for operational duties, and connect MCP when AI needs to access your workforce data. Most teams use a combination of the three.
Employees, contracts, payroll, expenses—sample data that allows you to test API calls, CLI commands and integrations without risking real records.
Try connector workflows, debug integrations and validate commands. All tests run against sandbox data.
Request access, sign in, and begin testing.
$ remote sandbox --init
Open a sandbox preloaded with employees, contracts, payroll and expenses. Test your connectors—API calls, CLI workflows and integrations—on realistic data without affecting production.
You sign in once, and that's all. Authentication, permissions, and compliance posture are preserved.
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 keep secrets, and your credentials never touch the tool in use.
Your Remote permissions apply equally to the CLI, API, and MCP. An employee will view employee records, an admin will see employer-level data, and no additional access is granted.
The CLI, API and MCP present defined, structured endpoints rather than direct database connections. Remote regulates responses so you receive orderly data without mass exports or unstructured dumps.
Remote transmits only the data you request, and solely to the tool or agent you authenticated. Your workforce data will not be used to train any AI provider's models.
The CLI, API and MCP operate under Remote's established security and compliance posture, with the same rigour you depend on.
If you're embedding Remote, creating integrations, or adding AI capabilities, Remote offers the appropriate interface for each workflow. The API supports long-lived integrations. The CLI enables your teams to build and run operations more quickly. MCP makes Remote accessible to AI agents.
Companies such as Personio and BambooHR use Remote to deliver global employment for their customers. The CLI helps your team trial workflows in the sandbox, diagnose problems, and execute operational tasks more quickly—accelerating implementation and support.
Maintain development on Remote's public API for the persistent integrations you've built. The CLI assists your team in testing endpoints, confirming workflows, and troubleshooting issues faster.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you're scripting, developing an integration, or attaching an AI tool, authentication remains straightforward and secure. There are no API keys to rotate and no secrets to keep. Your Remote permissions apply across every surface.
For individual users signing in through a browser (CLI, MCP).
Intended for direct customer scripts and backend automation.
Designed for partner integrations.
Sign in, follow the quickstart, and begin working in real time.