Everything in Remote is accessible through the interface that best matches 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 with the API, use the CLI for operational tasks, and connect MCP when you need AI 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 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.
Sign in once. That's all. Authentication, permissions, and the compliance posture transfer unchanged.
Sign in via your browser or use an API token, the same method you use to access Remote. We do not require you to create API keys or store secrets, and your credentials never touch the tool you're using.
The permissions granted in Remote apply equally to the CLI, API, and MCP. An employee can access employee data, an admin can access employer data, and no additional access is granted.
The CLI, API, and MCP present defined, structured endpoints rather than raw database access. Remote controls the responses so you receive orderly data without bulk exports or unstructured dumps.
Remote returns only the data you request, and only to the tool or agent you've authorised. 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 posture, with the same rigour you already trust.
If you are embedding Remote, building integrations, or adding AI features, Remote supplies the suitable interface for each workflow. The API supports durable integrations. The CLI helps your teams build and operate more quickly. MCP exposes Remote to AI agents.
Like Personio, BambooHR, and others, you deliver global employment for your customers through Remote. The CLI lets your team test workflows in a sandbox, debug issues, and run operational tasks faster, accelerating implementation and support.
Keep building on Remote's public API for the durable integrations you've built. The CLI helps your team test endpoints, validate workflows, and debug issues more quickly.
All three surfaces — API, CLI, and MCP — support flexible authentication. 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 logging in via 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.