Everything in Remote is accessible via the interface that best suits the way you build.
The Remote API is designed 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 build AI assistants that understand your organisation.
The API, CLI and MCP are built to work together.
Build production integrations with the API, use the CLI for operational work, and connect MCP when you want AI to access your workforce data. Most teams use a mix 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 — API calls, CLI workflows and integrations — on realistic data without touching production.
You sign in once. Authentication, permissions and the compliance posture are all carried through.
Sign in via your browser or use an API token, just like when you log into Remote. We don't require you to create API keys or store secrets, and your credentials never touch the tool.
Whatever permissions you hold in Remote apply across the CLI, API and MCP. An employee can see employee data, an admin can see employer data — and nothing beyond that.
The CLI, API and MCP provide defined, structured endpoints rather than direct database access. Remote controls the responses, so you receive tidy data without bulk exports or unstructured dumps.
Remote delivers only the data you request, and only to the tool or agent you've authorised. Your workforce data is not used to train any AI provider's models.
The CLI, API and MCP inherit Remote's established security and compliance posture, with the same rigour you already trust.
If you're embedding Remote, building integrations or adding AI functionality, Remote supplies the appropriate interface for each workflow. The API supports durable integrations. The CLI helps teams build and operate more quickly. MCP makes Remote accessible to AI agents.
As Personio, BambooHR and others do, you can offer global employment to your customers via 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 already built. The CLI helps your team test endpoints, validate workflows and troubleshoot issues faster.
All three surfaces (API, CLI, MCP) support flexible authentication. Whether you’re scripting, building an integration or connecting an AI tool, auth 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 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.